v3 standardize template file names

BETA-V3/docs/templates/architecture.md

@@ -58,7 +58,7 @@
 - docs/data-models.md
 - docs/environment-vars.md
 - docs/testing-strategy.md
-- docs/ui-ux-spec.md (if applicable)
+- docs/front-end-spec.md (if applicable)
 - ... (other relevant docs)
 
 ## Change Log

BETA-V3/docs/templates/prd.md

@@ -34,7 +34,7 @@
 
 ### User Experience (UX) Requirements (High-Level)
 
-{Describe the key aspects of the desired user experience. If a UI exists, link to `docs/ui-ux-spec.md` for details.}
+{Describe the key aspects of the desired user experience. If a UI exists, link to `docs/front-end-spec.md` for details.}
 
 - UX Goal 1: ...
 - UX Goal 2: ...
@@ -72,7 +72,7 @@
 - `docs/tech-stack.md`
 - `docs/api-reference.md`
 - `docs/testing-strategy.md`
-- `docs/ui-ux-spec.md` (if applicable)
+- `docs/front-end-spec.md` (if applicable)
 - ... (other relevant docs)
 
 ## Post-MVP / Future Enhancements

BETA-V3/gems-and-gpts/1-analyst.md

@@ -108,7 +108,7 @@ To perform deep research effectively, please be aware:
 
 ### Instructions
 
-- <critical_rule>State that you will use the attached `project-brief.txt` as the structure</critical_rule>
+- <critical_rule>State that you will use the attached `project-brief-tmpl.txt` as the structure</critical_rule>
 - <important_note>The interaction mode (Incremental by default, or YOLO if specified by the user as per Critical Start Up Operating Instruction 5) will determine how the following steps are handled.</important_note>
 - Guide through defining each section of the template:
   - <critical_rule>CRITICAL (in Incremental Mode): 1 section at a time ONLY</critical_rule>
@@ -123,7 +123,7 @@ To perform deep research effectively, please be aware:
 - Actively incorporate research findings if available
 - Help distinguish essential MVP features from future enhancements
 - <important_note>Follow the [output formatting rules](#output-formatting) to provide either drafts or the final project brief</important_note>
-- <critical_rule>Final Deliverable - Structure complete Project Brief document following the attached `project-brief.txt` template</critical_rule>
+- <critical_rule>Final Deliverable - Structure complete Project Brief document following the attached `project-brief-tmpl.txt` template</critical_rule>
 
 #### Output Formatting Critical Rules
 

BETA-V3/gems-and-gpts/2-pm.md

@@ -6,7 +6,7 @@
 
 1.  **Initial Assessment & Mode Recommendation:**
 
-    - Check for a complete PRD (e.g., `docs/PRD.md` or user-provided `prd.txt`/`prd.md`).
+    - Check for a complete PRD (e.g., `docs/PRD.md` or user-provided `prd-tmpl.txt`/`prd.md`).
       - If a complete PRD exists, recommend `Product Advisor Mode` or `Deep Research Phase` as the primary option.
       - If no PRD, or only high-level ideas/incomplete brief exists, recommend `Deep Research Phase` or `PRD Generation Mode`.
 
@@ -98,7 +98,7 @@ To perform deep research effectively, please be aware:
 
 ### Purpose
 
-- Transform inputs into core product definition documents conforming to the `prd.txt` template
+- Transform inputs into core product definition documents conforming to the `prd-tmpl.txt` template
 - Define clear MVP scope focused on essential functionality
 - Provide foundation for Architect and eventually AI dev agents
 
@@ -151,7 +151,7 @@ Remember as you follow the upcoming instructions:
    - Address deficiencies with user for input or suggested updates or corrections
    - Once complete and address, output the final checklist with all the checked items or skipped items, the section summary table, and any final notes. The checklist should have any findings that were discuss and resolved or ignored also. This will be a nice artifact for the user to keep.
 
-6. Produce the PRD with PM Prompt per the prd.txt utilizing the following guidance:
+6. Produce the PRD with PM Prompt per the prd-tmpl.txt utilizing the following guidance:
    **General Presentation & Content:**
 
    - Present Project Briefs (drafts or final) in a clean, full format.
@@ -171,7 +171,7 @@ Remember as you follow the upcoming instructions:
 
    - After this PRD is finalized, if the product described includes a user interface, strongly recommend to the user that the next critical step is to engage the **Design Architect** agent.
    - Specifically, advise them to use the Design Architect's **UI/UX Specification Mode**.
-   - Explain that the Design Architect will use this completed PRD as a primary input to collaboratively create the detailed `ui-ux-spec.txt` document, ensuring specialized expertise is applied to define the user experience and interface based on the solid foundation of this PRD.
+   - Explain that the Design Architect will use this completed PRD as a primary input to collaboratively create the detailed `front-end-spec-tmpl.txt` document, ensuring specialized expertise is applied to define the user experience and interface based on the solid foundation of this PRD.
      </important_note>
 
 ## Product Advisor Mode

BETA-V3/gems-and-gpts/3-architect.md

@@ -31,7 +31,7 @@
   - Always explain the rationale behind architectural decisions or recommendations.
   - Present options in small, digestible chunks, especially in incremental mode.
   - Provide clear context when switching between topics or architectural components.
-  - Reference key input documents like the PRD (including the "Initial Architect Prompt" section, if available), epic files, project brief, and any relevant research reports as needed during discussions. The `architecture-templates.txt` and `architect-checklist.txt` are core guiding documents for Phase 2.
+  - Reference key input documents like the PRD (including the "Initial Architect Prompt" section, if available), epic files, project brief, and any relevant research reports as needed during discussions. The `architecture-tmpl.txt` and `architect-checklist.txt` are core guiding documents for Phase 2.
 
 ---
 
@@ -93,7 +93,7 @@ To perform deep research effectively, please be aware:
 ### Purpose
 
 - To design a complete, robust, and well-documented technical architecture based on the project requirements (PRD, epics, brief), research findings, and user input.
-- To make definitive technology choices and articulate the rationale behind them, leveraging `architecture-templates.txt` as a structural guide.
+- To make definitive technology choices and articulate the rationale behind them, leveraging `architecture-tmpl.txt` as a structural guide.
 - To produce all necessary technical artifacts, ensuring the architecture is optimized for efficient implementation, particularly by AI developer agents, and validated against the `architect-checklist.txt`.
 
 ### Phase Persona
@@ -126,7 +126,7 @@ To perform deep research effectively, please be aware:
       - Document the confirmed choice and its rationale within the architecture document.
     - **Starter Templates:** If applicable and requested, research and recommend suitable starter templates or assess existing codebases. Explain alignment with project goals and seek user confirmation.
 
-4.  **Create Technical Artifacts (Incrementally, unless YOLO mode, guided by `architecture-template.txt`):**
+4.  **Create Technical Artifacts (Incrementally, unless YOLO mode, guided by `architecture-tmpl.txt`):**
 
     - For each artifact or section of the main Architecture Document:
       - **Explain Purpose:** Briefly describe the artifact/section's importance and what it will cover.
@@ -161,7 +161,7 @@ To perform deep research effectively, please be aware:
 
 ### Output Deliverables for Architecture Creation Phase
 
-- A comprehensive Architecture Document, structured according to the `architecture-template.txt` (which is all markdown) or an agreed-upon format, including all sections detailed above.
+- A comprehensive Architecture Document, structured according to the `architecture-tmpl.txt` (which is all markdown) or an agreed-upon format, including all sections detailed above.
 - Clear Mermaid diagrams for architecture overview, data models, etc.
 - A list of new or refined technical user stories/tasks ready for backlog integration.
 - A completed `architect-checklist.txt` (or a summary of its validation).

BETA-V3/gems-and-gpts/4-design-architect.md

@@ -6,9 +6,9 @@
 
     - Review available inputs (e.g., Project Brief, PRD, existing UI/UX specs, existing frontend architecture).
     - Present the user with the following primary operating modes:
-      - **A. UI/UX Specification Mode:** To define or refine the user experience, information architecture, user flows, and visual design guidelines. (Input: Brief, PRD; Output: Populated `ui-ux-spec.txt` content).
+      - **A. UI/UX Specification Mode:** To define or refine the user experience, information architecture, user flows, and visual design guidelines. (Input: Brief, PRD; Output: Populated `front-end-spec-tmpl.txt` content).
-      - **B. Frontend Architecture Mode:** To define the technical architecture for the frontend, including component strategy, state management, and API interactions. (Input: `ui-ux-spec.txt`, Main Architecture Document; Output: Populated `front-end-architecture.md` content).
+      - **B. Frontend Architecture Mode:** To define the technical architecture for the frontend, including component strategy, state management, and API interactions. (Input: `front-end-spec-tmpl.txt`, Main Architecture Document; Output: Populated `front-end-architecture.md` content).
-      - **C. AI Frontend Generation Prompt Mode:** To craft an optimized prompt for AI tools that generate frontend code. (Possible Inputs: `ui-ux-spec.txt`, `front-end-architecture.md`, Main Architecture Document; Output: Masterful prompt).
+      - **C. AI Frontend Generation Prompt Mode:** To craft an optimized prompt for AI tools that generate frontend code. (Possible Inputs: `front-end-spec-tmpl.txt`, `front-end-architecture.md`, Main Architecture Document; Output: Masterful prompt).
     - Confirm the selected mode with the user.
 
 2.  **Proceed to Selected Mode:**
@@ -22,7 +22,7 @@
 
 ### Purpose
 
-To collaboratively work with the user to define and document the User Interface (UI) and User Experience (UX) specifications for the project. This involves understanding user needs, defining information architecture, outlining user flows, and ensuring a solid foundation for visual design and frontend development. The output will populate the `ui-ux-spec.txt` template.
+To collaboratively work with the user to define and document the User Interface (UI) and User Experience (UX) specifications for the project. This involves understanding user needs, defining information architecture, outlining user flows, and ensuring a solid foundation for visual design and frontend development. The output will populate the `front-end-spec-tmpl.txt` template.
 
 ### Phase Persona
 
@@ -31,8 +31,8 @@ To collaboratively work with the user to define and document the User Interface
 
 ### Inputs
 
-- Project Brief (`project-brief.txt` or equivalent)
+- Project Brief (`project-brief-tmpl.txt` or equivalent)
-- Product Requirements Document (PRD) (`prd.txt` or equivalent)
+- Product Requirements Document (PRD) (`prd-tmpl.txt` or equivalent)
 - User feedback or research (if available)
 
 ### Key Activities & Instructions
@@ -40,38 +40,38 @@ To collaboratively work with the user to define and document the User Interface
 1.  **Understand Core Requirements:**
     - Review Project Brief and PRD to grasp project goals, target audience, key features, and any existing constraints.
     - Ask clarifying questions about user needs, pain points, and desired outcomes.
-2.  **Define Overall UX Goals & Principles (for `ui-ux-spec.txt`):**
+2.  **Define Overall UX Goals & Principles (for `front-end-spec-tmpl.txt`):**
     - Collaboratively establish and document:
       - Target User Personas (elicit details or confirm existing ones).
       - Key Usability Goals.
       - Core Design Principles for the project.
-3.  **Develop Information Architecture (IA) (for `ui-ux-spec.txt`):**
+3.  **Develop Information Architecture (IA) (for `front-end-spec-tmpl.txt`):**
     - Work with the user to create a Site Map or Screen Inventory.
     - Define the primary and secondary Navigation Structure.
     - Use Mermaid diagrams or lists as appropriate for the template.
-4.  **Outline Key User Flows (for `ui-ux-spec.txt`):**
+4.  **Outline Key User Flows (for `front-end-spec-tmpl.txt`):**
     - Identify critical user tasks from the PRD/brief.
     - For each flow:
       - Define the user's goal.
       - Collaboratively map out the steps (use Mermaid diagrams or detailed step-by-step descriptions).
       - Consider edge cases and error states.
-5.  **Discuss Wireframes & Mockups Strategy (for `ui-ux-spec.txt`):**
+5.  **Discuss Wireframes & Mockups Strategy (for `front-end-spec-tmpl.txt`):**
-    - Clarify where detailed visual designs will be created (e.g., Figma, Sketch) and ensure the `ui-ux-spec.txt` correctly links to these primary design files.
+    - Clarify where detailed visual designs will be created (e.g., Figma, Sketch) and ensure the `front-end-spec-tmpl.txt` correctly links to these primary design files.
     - If low-fidelity wireframes are needed first, offer to help conceptualize layouts for key screens.
-6.  **Define Component Library / Design System Approach (for `ui-ux-spec.txt`):**
+6.  **Define Component Library / Design System Approach (for `front-end-spec-tmpl.txt`):**
     - Discuss if an existing design system will be used or if a new one needs to be developed.
     - If new, identify a few foundational components to start with (e.g., Button, Input, Card) and their key states/behaviors at a high level. Detailed technical specs will be in `front-end-architecture.md`.
-7.  **Establish Branding & Style Guide Basics (for `ui-ux-spec.txt`):**
+7.  **Establish Branding & Style Guide Basics (for `front-end-spec-tmpl.txt`):**
     - If a style guide exists, link to it.
     - If not, collaboratively define placeholders for: Color Palette, Typography, Iconography, Spacing.
-8.  **Specify Accessibility (AX) Requirements (for `ui-ux-spec.txt`):**
+8.  **Specify Accessibility (AX) Requirements (for `front-end-spec-tmpl.txt`):**
     - Determine the target compliance level (e.g., WCAG 2.1 AA).
     - List any known specific AX requirements.
-9.  **Define Responsiveness Strategy (for `ui-ux-spec.txt`):**
+9.  **Define Responsiveness Strategy (for `front-end-spec-tmpl.txt`):**
     - Discuss and document key Breakpoints.
     - Describe the general Adaptation Strategy.
 10. **Output Generation:**
-    - Incrementally populate the sections of the `BETA-V3/gems-and-gpts/templates/ui-ux-spec.txt` file based on the discussions.
+    - Incrementally populate the sections of the `BETA-V3/gems-and-gpts/templates/front-end-spec-tmpl.txt` file based on the discussions.
     - Present sections to the user for review and confirmation.
     - Ensure all placeholder links and references are correctly noted.
 
@@ -81,7 +81,7 @@ To collaboratively work with the user to define and document the User Interface
 
 ### Purpose
 
-To define the technical architecture for the frontend application. This includes selecting appropriate patterns, structuring the codebase, defining component strategy, planning state management, outlining API interactions, and setting up testing and deployment approaches, all while adhering to the guidelines in `front-end-architecture.md` template.
+To define the technical architecture for the frontend application. This includes selecting appropriate patterns, structuring the codebase, defining component strategy, planning state management, outlining API interactions, and setting up testing and deployment approaches, all while adhering to the guidelines in `front-end-architecture-tmpl.txt` template.
 
 ### Phase Persona
 
@@ -90,8 +90,8 @@ To define the technical architecture for the frontend application. This includes
 
 ### Inputs
 
-- Product Requirements Document (PRD) (`prd.txt` or equivalent)
+- Product Requirements Document (PRD) (`prd-tmpl.txt` or equivalent)
-- Completed UI/UX Specification (`docs/ui-ux-spec.txt` or equivalent)
+- Completed UI/UX Specification (`docs/front-end-spec-tmpl.txt` or equivalent)
 - Main System Architecture Document (`docs/architecture.md` or equivalent) - The Design Architect should particularly note the overall system structure (Monorepo/Polyrepo, backend service architecture) detailed here, as it influences frontend patterns.
 - Primary Design Files (Figma, Sketch, etc., linked from UI/UX Spec)
 
@@ -138,7 +138,7 @@ To define the technical architecture for the frontend application. This includes
     - List key frontend-specific performance strategies to be employed.
 12. **Output Generation:**
 
-    - Incrementally populate the sections of the `BETA-V3/gems-and-gpts/templates/front-end-architecture.md` file.
+    - Incrementally populate the sections of the `BETA-V3/gems-and-gpts/templates/front-end-architecture-tmpl.txt` file.
     - Present sections for user review and confirmation.
 
 13. **Checklist Review and Finalization:**
@@ -169,7 +169,7 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
 
 ### Inputs
 
-- Completed UI/UX Specification (`ui-ux-spec.txt`)
+- Completed UI/UX Specification (`front-end-spec-tmpl.txt`)
 - Completed Frontend Architecture Document (`front-end-architecture.md`)
 - Main System Architecture Document (`architecture.md` - for API contracts and tech stack)
 - Primary Design Files (Figma, Sketch, etc. - for visual context if the tool can accept it or if descriptions are needed)
@@ -186,13 +186,13 @@ To generate a masterful, comprehensive, and optimized prompt that can be used wi
       - Mention the styling approach (e.g., Tailwind CSS, CSS Modules).
     - **Design System & Visuals:**
       - Reference the primary design files (e.g., Figma link).
-      - If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `ui-ux-spec.txt`).
+      - If the tool doesn't directly ingest design files, describe the overall visual style, color palette, typography, and key branding elements (from `front-end-spec-tmpl.txt`).
       - List any global UI components or design tokens that should be defined or adhered to.
     - **Application Structure & Routing:**
       - Describe the main pages/views and their routes (from `front-end-architecture.md` - Routing Strategy).
-      - Outline the navigation structure (from `ui-ux-spec.txt`).
+      - Outline the navigation structure (from `front-end-spec-tmpl.txt`).
     - **Key User Flows & Page-Level Interactions:**
-      - For a few critical user flows (from `ui-ux-spec.txt`):
+      - For a few critical user flows (from `front-end-spec-tmpl.txt`):
         - Describe the sequence of user actions and expected UI changes on each relevant page.
         - Specify API calls to be made (referencing API endpoints from the main `architecture.md`) and how data should be displayed or used.
     - **Component Generation Instructions (Iterative or Key Components):**

BETA-V3/gems-and-gpts/5-po-sm.md

@@ -39,7 +39,7 @@
 <reference_documents>
 
 - Epic Files: `docs/epicN.md`
-- Story Template: `templates/story-template.txt`
+- Story Template: `templates/story-tmpl.txt`
 - PO Checklist: `templates/po-checklist.txt`
 - Story Draft Checklist: `templates/story-draft-checklist.txt`
 - Technical References:
@@ -51,7 +51,7 @@
   - Coding Standards: `docs/coding-standards.md`
   - Environment Variables: `docs/environment-vars.md`
   - Testing Strategy: `docs/testing-strategy.md`
-  - UI/UX Specifications: `docs/ui-ux-spec.md` (if applicable)
+  - UI/UX Specifications: `docs/front-end-spec.md` (if applicable)
     </reference_documents>
 
 <communication_style>

BETA-V3/gems-and-gpts/checklists/frontend-architecture-checklist.txt

@@ -1,7 +1,7 @@
 # Frontend Architecture Document Review Checklist
 
 ## Purpose
-This checklist is for the Design Architect to use after completing the "Frontend Architecture Mode" and populating the `front-end-architecture.txt` (or `.md`) document. It ensures all sections are comprehensively covered and meet quality standards before finalization.
+This checklist is for the Design Architect to use after completing the "Frontend Architecture Mode" and populating the `front-end-architecture-tmpl.txt` (or `.md`) document. It ensures all sections are comprehensively covered and meet quality standards before finalization.
 
 ---
 

BETA-V3/gems-and-gpts/instruction.md

@@ -11,25 +11,25 @@
 ### Analyst (BA/RA)
 
 - Instructions: 1-analyst-gem.md pasted into instructions
-- Knowledge: templates/project-brief.txt
+- Knowledge: templates/project-brief-tmpl.txt
 - During Chat - Mode 1 - 2.5 Pro Deep Research recommended. Mode 2 2.5 Pro Thinking Mode + optional mode 1 deep research attached.
 
 ### Product Manager (PM)
 
 - Instructions: 2-pm-gem.md pasted into instructions
-- Knowledge: templates/prd.txt, templates/epicN.txt, templates/ui-ux-spec.txt, templates/pm-checklist.txt
+- Knowledge: templates/prd-tmpl.txt, templates/epicN.txt, templates/front-end-spec-tmpl.txt, templates/pm-checklist.txt
 - During Chat - Mode 1 - 2.5 Pro Deep Research recommended. Mode 2 2.5 Pro Thinking Mode. Start by also attaching the product brief.
 
 ### Architect
 
 - Instructions: 3-architect-gem.md pasted into instructions
-- Knowledge: templates/architecture-templates.txt, templates/architect-checklist.txt
+- Knowledge: templates/architecture-tmpl.txt, templates/architect-checklist.txt
 - During Chat - Mode 1 - 2.5 Pro Deep Research recommended. Mode 2 2.5 Pro Thinking Mode. Start by also attaching the product brief, PRD, and any generated Epic files. If architecture deep research was done as mode 1, attach it to the new chat. Also if there was deep research from the PRD that is not fully distilled in the PRD (deep technical details or solutions), provide to the architect.
 
 ### PO + SM
 
 - Instructions: 4-po-sm-gem.md pasted into instructions
-- Knowledge: templates/story-template.txt, templates/po-checklist.txt
+- Knowledge: templates/story-tmpl.txt, templates/po-checklist.txt
 - This is optional as a Gem - unlike the workflow within the IDE, using this will generate all remaining stories as one output, instead generating each story when its ready to be worked on through completion. There is ONE main use case for this beyond the obvious generating the artifacts to work on one at a time.
   - The output of this can easily be passed to a new chat with this PO + SM gem or custom GPT and asked to deeply think or analyze through all of the extensive details to spot potential issues gaps, or inconsistences. I have not done this as I prefer to just generate and build 1 story at a time - so the utility of this I have not fully exhausted - but its an interesting idea.
 - During chat: Recommend starting chat by providing all possible artifacts output from previous stages - if a file limit is hit, you can attach as a folder in thinking mode for 2.5 pro - or combine documents. The SM needs latest versions of `prd.md`, `architecture.md`, the _technically enriched_ `epicN.md...` files, and relevant reference documents the architecture references, provided after initial PM/Architect collaboration and refinement.

BETA-V3/gems-and-gpts/templates/front-end-architecture-tmpl.txt

@@ -37,7 +37,7 @@
 { This document details the technical architecture specifically for the frontend of {Project Name}. It complements the main {Project Name} Architecture Document and the UI/UX Specification. The goal is to provide a clear blueprint for frontend development, ensuring consistency, maintainability, and alignment with the overall system design and user experience goals. }
 
 - **Link to Main Architecture Document:** {e.g., `docs/architecture.md`} (Note: The overall system architecture, including Monorepo/Polyrepo decisions and backend structure, will influence frontend choices, especially around shared code or API interaction patterns.)
-- **Link to UI/UX Specification:** {e.g., `docs/ui-ux-spec.md`}
+- **Link to UI/UX Specification:** {e.g., `docs/front-end-spec.md`}
 - **Link to Primary Design Files (Figma, Sketch, etc.):** {From UI/UX Spec}
 - **Link to Deployed Storybook / Component Showcase (if applicable):** {URL}