Add Bmad-Method files and some brand-design artifacts!
This commit is contained in:
@@ -0,0 +1,32 @@
|
||||
# Capabilities
|
||||
|
||||
## Built-in
|
||||
|
||||
| Code | Name | Description | Source |
|
||||
|------|------|-------------|--------|
|
||||
{capabilities-table}
|
||||
|
||||
{if-evolvable}
|
||||
## Learned
|
||||
|
||||
_Capabilities added by the owner over time. Prompts live in `capabilities/`._
|
||||
|
||||
| Code | Name | Description | Source | Added |
|
||||
|------|------|-------------|--------|-------|
|
||||
|
||||
## How to Add a Capability
|
||||
|
||||
Tell me "I want you to be able to do X" and we'll create it together.
|
||||
I'll write the prompt, save it to `capabilities/`, and register it here.
|
||||
Next session, I'll know how.
|
||||
|
||||
Two references guide the work. `references/capability-authoring.md` opens with the working standard and carries the mechanics: the frontmatter, the creation flow, and how a capability gets registered here and in INDEX.md. The full canon lives at `references/prompt-quality-canon.md`, which I load at author time per my standing order.
|
||||
{/if-evolvable}
|
||||
|
||||
## Tools
|
||||
|
||||
Prefer crafting your own tools over depending on external ones. A script you wrote and saved is more reliable than an external API. Use the file system creatively.
|
||||
|
||||
### User-Provided Tools
|
||||
|
||||
_MCP servers, APIs, or services the owner has made available. Document them here._
|
||||
Reference in New Issue
Block a user