diff --git a/.vscode/settings.json b/.vscode/settings.json index 09581953..e3eb4b9b 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -7,7 +7,42 @@ "chat.tools.autoApprove": false, "cSpell.words": [ "Agentic", + "atlasing", + "Biostatistician", + "Cordova", + "customresourcedefinitions", + "dashboarded", + "Decisioning", + "eksctl", "elicitations", - "Shardable" + "filecomplete", + "fintech", + "fluxcd", + "gamedev", + "gitops", + "implementability", + "inclusivity", + "ingressgateway", + "istioctl", + "metroidvania", + "NACLs", + "nodegroup", + "platformconfigs", + "Playfocus", + "playtesting", + "pointerdown", + "pointerup", + "replayability", + "roguelike", + "roomodes", + "Runbook", + "runbooks", + "Shardable", + "Softlock", + "speedrunner", + "tekton", + "tilemap", + "tileset", + "VNET" ] } \ No newline at end of file diff --git a/bmad-core/data/bmad-kb.md b/bmad-core/data/bmad-kb.md index fd024c53..99b67b22 100644 --- a/bmad-core/data/bmad-kb.md +++ b/bmad-core/data/bmad-kb.md @@ -362,7 +362,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package diff --git a/dist/agents/analyst.txt b/dist/agents/analyst.txt index 912c9960..be153cee 100644 --- a/dist/agents/analyst.txt +++ b/dist/agents/analyst.txt @@ -2318,7 +2318,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package diff --git a/dist/agents/architect.txt b/dist/agents/architect.txt index 7bbe7f34..f3952072 100644 --- a/dist/agents/architect.txt +++ b/dist/agents/architect.txt @@ -1963,7 +1963,7 @@ Document the choice and key services that will be used.]] ### Repository Structure -[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask quetsions to the user if unsure: +[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask questions to the user if unsure: 1. For modern fullstack apps, monorepo is often preferred 2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces) diff --git a/dist/agents/bmad-master.txt b/dist/agents/bmad-master.txt index 1e5cef67..6537c251 100644 --- a/dist/agents/bmad-master.txt +++ b/dist/agents/bmad-master.txt @@ -5347,7 +5347,7 @@ Document the choice and key services that will be used.]] ### Repository Structure -[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask quetsions to the user if unsure: +[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask questions to the user if unsure: 1. For modern fullstack apps, monorepo is often preferred 2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces) @@ -9127,7 +9127,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package diff --git a/dist/agents/bmad-orchestrator.txt b/dist/agents/bmad-orchestrator.txt index 247a1ed9..ccd56066 100644 --- a/dist/agents/bmad-orchestrator.txt +++ b/dist/agents/bmad-orchestrator.txt @@ -1347,7 +1347,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package diff --git a/dist/teams/team-all.txt b/dist/teams/team-all.txt index a08818ea..e4aa0e2c 100644 --- a/dist/teams/team-all.txt +++ b/dist/teams/team-all.txt @@ -1836,7 +1836,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package @@ -5352,7 +5352,7 @@ Document the choice and key services that will be used.]] ### Repository Structure -[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask quetsions to the user if unsure: +[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask questions to the user if unsure: 1. For modern fullstack apps, monorepo is often preferred 2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces) diff --git a/dist/teams/team-fullstack.txt b/dist/teams/team-fullstack.txt index 5faf08a6..816d6a30 100644 --- a/dist/teams/team-fullstack.txt +++ b/dist/teams/team-fullstack.txt @@ -1684,7 +1684,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package @@ -7296,7 +7296,7 @@ Document the choice and key services that will be used.]] ### Repository Structure -[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask quetsions to the user if unsure: +[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask questions to the user if unsure: 1. For modern fullstack apps, monorepo is often preferred 2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces) diff --git a/dist/teams/team-ide-minimal.txt b/dist/teams/team-ide-minimal.txt index ff9801e9..9c879ae4 100644 --- a/dist/teams/team-ide-minimal.txt +++ b/dist/teams/team-ide-minimal.txt @@ -1582,7 +1582,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package diff --git a/dist/teams/team-no-ui.txt b/dist/teams/team-no-ui.txt index adf47e98..53cae765 100644 --- a/dist/teams/team-no-ui.txt +++ b/dist/teams/team-no-ui.txt @@ -1622,7 +1622,7 @@ The BMad-Method is built around a modular architecture centered on the `bmad-cor #### Web UI Environment -- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assest with an orchestrating agent +- Uses pre-built bundles from `dist/teams` for stand alone 1 upload files for all agents and their assets with an orchestrating agent - Single text files containing all agent dependencies are in `dist/agents/` - these are unnecessary unless you want to create a web agent that is only a single agent and not a team - Created by the web-builder tool for upload to web interfaces - Provides complete context in one package @@ -6764,7 +6764,7 @@ Document the choice and key services that will be used.]] ### Repository Structure -[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask quetsions to the user if unsure: +[[LLM: Define the repository approach based on PRD requirements and platform choice, explain your rationale or ask questions to the user if unsure: 1. For modern fullstack apps, monorepo is often preferred 2. Consider tooling (Nx, Turborepo, Lerna, npm workspaces)