new uxui design agent and architect improvements

BETA-V3/gems-and-gpts/templates/prd.txt

@@ -12,7 +12,19 @@ You should have a good idea at this point, but clarify suggest question and expl
 
 ## User Interaction and Design Goals
 
-If there is a UX/UI Component, we want to work with the user to elicit enough information to detail the UI look and feel, screens, interaction, functionality so that we can produce the UI as needed.
+{
+If the product includes a User Interface (UI), this section captures the Product Manager's high-level vision and goals for the User Experience (UX). This information will serve as a crucial starting point and brief for the Design Architect.
+
+Consider and elicit information from the user regarding:
+- **Overall Vision & Experience:** What is the desired look and feel (e.g., "modern and minimalist," "friendly and approachable," "data-intensive and professional")? What kind of experience should users have?
+- **Key Interaction Paradigms:** Are there specific ways users will interact with core features (e.g., "drag-and-drop interface for X," "wizard-style setup for Y," "real-time dashboard for Z")?
+- **Core Screens/Views (Conceptual):** From a product perspective, what are the most critical screens or views necessary to deliver the MVP's value? (e.g., "Login Screen," "Main Dashboard," "Item Detail Page," "Settings Page").
+- **Accessibility Aspirations:** Any known high-level accessibility goals (e.g., "must be usable by screen reader users").
+- **Branding Considerations (High-Level):** Any known branding elements or style guides that must be incorporated?
+- **Target Devices/Platforms:** (e.g., "primarily web desktop," "mobile-first responsive web app").
+
+This section is not intended to be a detailed UI specification but rather a product-focused brief to guide the subsequent detailed work by the Design Architect, who will create the comprehensive UI/UX Specification document.
+}
 
 ## Technical Assumptions
 
@@ -22,7 +34,7 @@ This is where we can list information mostly to be used by the architect to prod
 
 How will we validate functionality beyond unit testing? Will we want manual scripts or testing, e2e, integration etc... figure this out from the user to populate this section
 
-## Epic Overview (MVP / Current Version)
+## Epic Overview
 
 - **Epic {#}: {Title}**
     - Goal: {A concise 1-2 sentence statement describing the primary objective and value of this Epic.}
@@ -37,97 +49,9 @@ How will we validate functionality beyond unit testing? Will we want manual scri
     - Story {#}: As a {type of user/system}, I want {to perform an action / achieve a goal} so that {I can realize a benefit / achieve a reason}.
         - {Acceptance Criteria List}
 
---- OPTIONAL UI UX SECTION START ----
-
-## UI/UX Specification
-
-### Overall UX Goals & Principles
-
-- **Target User Personas:** {Reference personas or briefly describe key user types and their goals.}
-- **Usability Goals:** {e.g., Ease of learning, efficiency of use, error prevention.}
-- **Design Principles:** {List 3-5 core principles guiding the UI/UX design - e.g., "Clarity over cleverness", "Consistency", "Provide feedback".}
-
-### Information Architecture (IA)
-
-- **Site Map / Screen Inventory:**
-  ```mermaid
-  graph TD
-      A[Homepage] --> B(Dashboard);
-      A --> C{Settings};
-      B --> D[View Details];
-      C --> E[Profile Settings];
-      C --> F[Notification Settings];
-  ```
-  _(Or provide a list of all screens/pages)_
-- **Navigation Structure:** {Describe primary navigation (e.g., top bar, sidebar), secondary navigation, breadcrumbs, etc.}
-
-### User Flows
-
-{Detail key user tasks. Use diagrams or descriptions.}
-
-#### {User Flow Name, e.g., User Login}
-
-- **Goal:** {What the user wants to achieve.}
-- **Steps / Diagram:**
-  ```mermaid
-  graph TD
-      Start --> EnterCredentials[Enter Email/Password];
-      EnterCredentials --> ClickLogin[Click Login Button];
-      ClickLogin --> CheckAuth{Auth OK?};
-      CheckAuth -- Yes --> Dashboard;
-      CheckAuth -- No --> ShowError[Show Error Message];
-      ShowError --> EnterCredentials;
-  ```
-  _(Or: Link to specific flow diagram in Figma/Miro)_
-
-#### {Another User Flow Name}
-
-{...}
-
-### Wireframes & Mockups
-
-{Reference the main design file link above. Optionally embed key mockups or describe main screen layouts.}
-
-- **Screen / View Name 1:** {Description of layout and key elements. Link to specific Figma frame/page.}
-- **Screen / View Name 2:** {...}
-
-### Component Library / Design System Reference
-
-{Link to the primary source (Storybook, Figma Library). If none exists, define key components here.}
-
-#### {Component Name, e.g., Primary Button}
-
-- **Appearance:** {Reference mockup or describe styles.}
-- **States:** {Default, Hover, Active, Disabled, Loading.}
-- **Behavior:** {Interaction details.}
-
-#### {Another Component Name}
-
-{...}
-
-### Branding & Style Guide Reference
-
-{Link to the primary source or define key elements here.}
-
-- **Color Palette:** {Primary, Secondary, Accent, Feedback colors (hex codes).}
-- **Typography:** {Font families, sizes, weights for headings, body, etc.}
-- **Iconography:** {Link to icon set, usage notes.}
-- **Spacing & Grid:** {Define margins, padding, grid system rules.}
-
-### Accessibility (AX) Requirements
-
-- **Target Compliance:** {e.g., WCAG 2.1 AA}
-- **Specific Requirements:** {Keyboard navigation patterns, ARIA landmarks/attributes for complex components, color contrast minimums.}
-
-### Responsiveness
-
-- **Breakpoints:** {Define pixel values for mobile, tablet, desktop, etc.}
-- **Adaptation Strategy:** {Describe how layout and components adapt across breakpoints. Reference designs.}
-
---- OPTIONAL UI UX SECTION END ----
-
 ## Key Reference Documents
-{Will be populated at a later time}
+
+{ This section will be created later, from the sections prior to this being carved up into smaller documents }
 
 ## Out of Scope Ideas Post MVP