@siliconoid/agentkit 0.1.0

package/templates/bmad/gemini/commands/bmad-workflow-bmm-code-review.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: code-review"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/code-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-correct-course.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: correct-course"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-architecture.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: create-architecture"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-epics-and-stories.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: create-epics-and-stories"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-excalidraw-dataflow.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: create-excalidraw-dataflow"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-excalidraw-diagram.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: create-excalidraw-diagram"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-excalidraw-flowchart.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: create-excalidraw-flowchart"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-excalidraw-wireframe.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: create-excalidraw-wireframe"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-product-brief.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: create-product-brief"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-story.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: create-story"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-create-ux-design.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: create-ux-design"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-dev-story.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: dev-story"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-document-project.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: document-project"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/document-project/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-generate-project-context.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: generate-project-context"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-prd.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: prd"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-quick-dev.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: quick-dev"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-quick-spec.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: quick-spec"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-research.toml

@@ -0,0 +1,4 @@
+description = "BMAD BMM Workflow: research"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/bmm/workflows/1-analysis/research/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-retrospective.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: retrospective"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-sprint-planning.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: sprint-planning"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-sprint-status.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: sprint-status"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-atdd.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-atdd"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/atdd/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-automate.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-automate"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/automate/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-ci.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-ci"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/ci/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-framework.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-framework"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/framework/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-nfr.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-nfr"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-test-design.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-test-design"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-design/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-test-review.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-test-review"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/test-review/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-testarch-trace.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: testarch-trace"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/testarch/trace/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-workflow-init.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: workflow-init"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/init/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/workflow-status/init/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-bmm-workflow-status.toml

@@ -0,0 +1,12 @@
+description = "BMAD BMM Workflow: workflow-status"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
+
+<steps CRITICAL="TRUE">
+1. Always LOAD the FULL @_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @_bmad/bmm/workflows/workflow-status/workflow.yaml
+3. Pass the yaml path _bmad/bmm/workflows/workflow-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
+5. Save outputs after EACH section when generating any documents from templates
+</steps>
+"""

package/templates/bmad/gemini/commands/bmad-workflow-core-brainstorming.toml

@@ -0,0 +1,4 @@
+description = "BMAD CORE Workflow: brainstorming"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/bmad/gemini/commands/bmad-workflow-core-party-mode.toml

@@ -0,0 +1,4 @@
+description = "BMAD CORE Workflow: party-mode"
+prompt = """
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!
+"""

package/templates/frameworks/nextjs-app/.ai/rules/01-project-overview.md

@@ -0,0 +1,25 @@
+# Project Overview
+
+**{{projectName}}** — {{projectDescription}}
+
+## Tech Stack
+
+| Category | Technology | Version |
+|----------|-----------|---------|
+| Framework | Next.js (App Router) | {{frameworkVersion}} |
+| UI Library | React | {{reactVersion}} |
+| Language | {{primaryLanguage}} | {{typescriptVersion}} |
+| State Management | {{stateManagement}} | — |
+| UI Components | {{uiLibrary}} | — |
+| Styling | {{cssApproach}} | — |
+| HTTP Client | {{httpClient}} | — |
+| Testing | {{testingFramework}} | — |
+| Build Tool | {{buildTool}} | — |
+| Linter | {{linter}} | — |
+| Package Manager | {{packageManager}} | — |
+
+## Technology Constraints
+
+- **Next.js App Router** — all routing via `app/` directory
+- Server Components by default, `'use client'` directive for client components
+- Server Actions for mutations

package/templates/frameworks/nextjs-app/.ai/rules/02-architecture.md

@@ -0,0 +1,36 @@
+# Architecture
+
+## Overview
+
+**{{projectName}}** is a Next.js application using the App Router pattern.
+
+## Page Structure
+
+All routes are in `app/`:
+
+```
+app/
+├── layout.tsx          # Root layout
+├── page.tsx            # Home page
+├── loading.tsx         # Loading UI
+├── error.tsx           # Error boundary
+└── feature/
+    ├── page.tsx        # Feature page
+    └── layout.tsx      # Nested layout
+```
+
+## Server vs Client Components
+
+- Default: Server Components (no `'use client'`)
+- Add `'use client'` only when needed (hooks, event handlers, browser APIs)
+- Keep client components as leaf nodes
+
+## Data Fetching
+
+- Server Components: `async` component with direct `fetch()` or database calls
+- Client Components: React Query, SWR, or `useEffect`
+- Mutations: Server Actions (`'use server'`)
+
+## State Management
+
+Describe how application state is managed.

package/templates/frameworks/nextjs-app/.ai/rules/07-react.md

@@ -0,0 +1,56 @@
+# React
+
+## Component Structure
+
+Each component lives in its own directory:
+
+```
+components/common/my-component/
+├── index.tsx              # Component implementation
+├── index.module.scss      # Scoped styles
+└── (optional sub-files)
+```
+
+## Function Components Only
+
+Use function components for all code.
+
+## Server Components (default)
+
+```typescript
+// No 'use client' — this is a Server Component
+export default async function MyPage() {
+  const data = await fetchData()
+  return <div>{data.title}</div>
+}
+```
+
+## Client Components
+
+```typescript
+'use client'
+
+import { useState } from 'react'
+
+export function Counter() {
+  const [count, setCount] = useState(0)
+  return <button onClick={() => setCount(c => c + 1)}>{count}</button>
+}
+```
+
+## Props Handling
+
+Destructure props in the function signature. Use default parameter values.
+
+## Event Handler Naming
+
+| Type | Prefix | Example |
+|------|--------|---------|
+| Internal handler | `handle` | `handleClick`, `handleSubmit` |
+| Prop callback | `on` | `onClick`, `onSubmit` |
+
+## Hooks Best Practices
+
+- Only in Client Components (`'use client'`)
+- **One effect per concern**
+- **Always clean up** subscriptions, timers, and listeners

package/templates/frameworks/nextjs-pages/.ai/rules/01-project-overview.md

@@ -0,0 +1,25 @@
+# Project Overview
+
+**{{projectName}}** — {{projectDescription}}
+
+## Tech Stack
+
+| Category | Technology | Version |
+|----------|-----------|---------|
+| Framework | Next.js (Pages Router) | {{frameworkVersion}} |
+| UI Library | React | {{reactVersion}} |
+| Language | {{primaryLanguage}} | {{typescriptVersion}} |
+| State Management | {{stateManagement}} | — |
+| UI Components | {{uiLibrary}} | — |
+| Styling | {{cssApproach}} | — |
+| HTTP Client | {{httpClient}} | — |
+| Testing | {{testingFramework}} | — |
+| Build Tool | {{buildTool}} | — |
+| Linter | {{linter}} | — |
+| Package Manager | {{packageManager}} | — |
+
+## Technology Constraints
+
+- **Next.js Pages Router** — all routing via `pages/` directory
+- **No App Router** — do not use `app/` directory features
+- SSR via `getServerSideProps`, SSG via `getStaticProps`

package/templates/frameworks/nextjs-pages/.ai/rules/02-architecture.md

@@ -0,0 +1,30 @@
+# Architecture
+
+## Overview
+
+**{{projectName}}** is a Next.js application using the Pages Router pattern.
+
+## Page Structure
+
+All pages are in `src/pages/` (or `pages/`):
+
+```typescript
+import { GetServerSideProps } from 'next'
+
+export const getServerSideProps: GetServerSideProps = async ({ locale }) => ({
+  props: {
+    // SSR data
+  },
+})
+
+const MyPage = () => { ... }
+export default MyPage
+```
+
+## Request/Response Architecture
+
+Describe your API patterns and data fetching strategy.
+
+## State Management
+
+Describe how application state is managed.

package/templates/frameworks/nextjs-pages/.ai/rules/07-react.md

@@ -0,0 +1,51 @@
+# React
+
+## Component Structure
+
+Each component lives in its own directory:
+
+```
+components/common/my-component/
+├── index.tsx              # Component implementation
+├── index.module.scss      # Scoped styles
+└── (optional sub-files)
+```
+
+## Function Components Only
+
+Use function components for all new code.
+
+## Next.js Pages Router
+
+All pages use the Pages Router pattern:
+
+```typescript
+import { GetServerSideProps } from 'next'
+
+export const getServerSideProps: GetServerSideProps = async ({ locale }) => ({
+  props: {
+    // SSR data fetching
+  },
+})
+
+const MyPage = () => { ... }
+export default MyPage
+```
+
+## Props Handling
+
+Destructure props in the function signature. Use default parameter values.
+
+## Event Handler Naming
+
+| Type | Prefix | Example |
+|------|--------|---------|
+| Internal handler | `handle` | `handleClick`, `handleSubmit` |
+| Prop callback | `on` | `onClick`, `onSubmit` |
+
+## Hooks Best Practices
+
+- **One effect per concern**
+- **Always clean up** subscriptions, timers, and listeners
+- `useCallback` — wrap callbacks passed to child components
+- `useMemo` — use for computationally expensive derived values

package/templates/frameworks/nodejs/.ai/rules/01-project-overview.md

@@ -0,0 +1,20 @@
+# Project Overview
+
+**{{projectName}}** — {{projectDescription}}
+
+## Tech Stack
+
+| Category | Technology | Version |
+|----------|-----------|---------|
+| Runtime | Node.js | {{nodeVersion}} |
+| Framework | {{frameworkDisplay}} | {{frameworkVersion}} |
+| Language | {{primaryLanguage}} | {{typescriptVersion}} |
+| HTTP Client | {{httpClient}} | — |
+| Testing | {{testingFramework}} | — |
+| Build Tool | {{buildTool}} | — |
+| Linter | {{linter}} | — |
+| Package Manager | {{packageManager}} | — |
+
+## Technology Constraints
+
+- List any version constraints or limitations here