Brian Madison 1868477238 refactor(config): replace hardcoded .bmad paths with {bmad_folder} placeholder
Remove hardcoded .bmad folder references throughout documentation and source files, replacing them with the configurable {bmad_folder} placeholder. This change enables users to customize the BMAD installation folder name via configuration, improving flexibility and reducing coupling to a specific directory structure.

Changes include:
- Update all documentation to reference {bmad_folder} instead of .bmad
- Remove legacy configuration files from .bmad and .claude directories
- Update workflow.xml and CLI documentation with new placeholder syntax
2025-11-12 20:22:47 -06:00

749 B

BMAD Method - Cursor Instructions

Activating Agents

BMAD agents are installed in .cursor/rules/bmad/ as MDC rules.

How to Use

  1. Reference in Chat: Use @{bmad_folder}/{module}/agents/{agent-name}
  2. Include Entire Module: Use @{bmad_folder}/{module}
  3. Reference Index: Use @{bmad_folder}/index for all available agents

Examples

@{bmad_folder}/core/agents/dev - Activate dev agent
@{bmad_folder}/bmm/agents/architect - Activate architect agent
@{bmad_folder}/core - Include all core agents/tasks

Notes

  • Rules are Manual type - only loaded when explicitly referenced
  • No automatic context pollution
  • Can combine multiple agents: @{bmad_folder}/core/agents/dev @{bmad_folder}/core/agents/test