fix: enhanced user guide with better diagrams

This commit is contained in:
Brian Madison
2025-07-19 20:54:41 -05:00
parent e44271b191
commit c445962f25
10 changed files with 145 additions and 1037 deletions

View File

@@ -6,8 +6,9 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Claude Code** as your IDE. This creates: When running `npx bmad-method install`, select **Claude Code** as your IDE. This creates:
- `.bmad-core/` folder with all agents - `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.claude/commands/BMad` folder with agent command files (`.md`) - `.claude/commands/BMad/agents` folder with agent command files (`.md`)
- `.claude/commands/BMad/tasks` folder with stand alone task files (`.md`)
## Using BMad Agents in Claude Code ## Using BMad Agents in Claude Code

View File

@@ -6,6 +6,7 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Cline** as your IDE. This creates: When running `npx bmad-method install`, select **Cline** as your IDE. This creates:
- `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.clinerules/` directory with numbered agent rule files (`.md`) - `.clinerules/` directory with numbered agent rule files (`.md`)
- Agents ordered by priority (bmad-master first) - Agents ordered by priority (bmad-master first)

View File

@@ -6,7 +6,7 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Cursor** as your IDE. This creates: When running `npx bmad-method install`, select **Cursor** as your IDE. This creates:
- `.bmad-core/` folder with all agents - `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.cursor/rules/` folder with agent rule files (`.mdc`) - `.cursor/rules/` folder with agent rule files (`.mdc`)
## Using BMad Agents in Cursor ## Using BMad Agents in Cursor

View File

@@ -6,6 +6,7 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Gemini CLI** as your IDE. This creates: When running `npx bmad-method install`, select **Gemini CLI** as your IDE. This creates:
- `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.gemini/bmad-method/` directory with all agent context in GEMINI.md file - `.gemini/bmad-method/` directory with all agent context in GEMINI.md file
## Using BMad Agents with Gemini CLI ## Using BMad Agents with Gemini CLI

View File

@@ -6,9 +6,9 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **GitHub Copilot** as your IDE. This command will perform the following actions: When running `npx bmad-method install`, select **GitHub Copilot** as your IDE. This command will perform the following actions:
- Create the `.bmad-core/` directory with all the agent rule files. - `.bmad-core/` folder with all agents, tasks, templates and other data files
- Create the `.vscode/` directory and add a `settings.json` file if it does not already exist, and add the basic configuration to enable GitHub Copilot's agent mode. - Creates the `.vscode/` directory and add a `settings.json` file if it does not already exist, and add the basic configuration to enable GitHub Copilot's agent mode.
- Create a chatmodes file under your .github folder for each specific agent being added - Creates a chatmodes file under your .github folder for each specific agent being added
## Using BMAD Agents in GitHub Copilot ## Using BMAD Agents in GitHub Copilot

View File

@@ -6,7 +6,7 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Roo Code** as your IDE. This creates: When running `npx bmad-method install`, select **Roo Code** as your IDE. This creates:
- `.bmad-core/` folder with all agents - `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.roomodes` file in project root with custom modes - `.roomodes` file in project root with custom modes
## Roo Code-Specific Features ## Roo Code-Specific Features

View File

@@ -6,7 +6,7 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Trae** as your IDE. This creates: When running `npx bmad-method install`, select **Trae** as your IDE. This creates:
- `.bmad-core/` folder with all agents - `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.trae/rules/` folder with agent rule files (`.md`) - `.trae/rules/` folder with agent rule files (`.md`)
## Using BMad Agents in Trae ## Using BMad Agents in Trae

View File

@@ -6,7 +6,7 @@ For the complete workflow, see the [BMad Workflow Guide](../bmad-workflow-guide.
When running `npx bmad-method install`, select **Windsurf** as your IDE. This creates: When running `npx bmad-method install`, select **Windsurf** as your IDE. This creates:
- `.bmad-core/` folder with all agents - `.bmad-core/` folder with all agents, tasks, templates and other data files
- `.windsurf/rules/` folder with agent rule files (`.md`) - `.windsurf/rules/` folder with agent rule files (`.md`)
## Using BMad Agents in Windsurf ## Using BMad Agents in Windsurf

View File

@@ -35,7 +35,8 @@ Use Google's Gemini for collaborative planning with the full team:
1. **Open [Google Gems](https://gemini.google.com/gems/view)** 1. **Open [Google Gems](https://gemini.google.com/gems/view)**
2. **Create a new Gem**: 2. **Create a new Gem**:
- Give it a title and description (e.g., "BMad Team Fullstack") - Give it a title (e.g., "BMad Team Fullstack")
- In the description enter:
3. **Load team-fullstack**: 3. **Load team-fullstack**:
- Copy contents of: `web-bundles/teams/team-fullstack.txt` from your project - Copy contents of: `web-bundles/teams/team-fullstack.txt` from your project
- Paste this content into the Gem setup to configure the team - Paste this content into the Gem setup to configure the team

File diff suppressed because it is too large Load Diff