How packs work
{"content":"Once you know what comes in the built-in packs, use these pages to understand the underlying architecture: how source files become importable archives, how `.agent.yaml` definitions bind agents to behavior, and how annotated Markdown becomes reusable capabilities and prompts.\n\n{{\u003c cards \u003e}}\n {{\u003c card link=\"./pack-structure/\" title=\"Pack structure\" subtitle=\"Source directories, manifests, generated archives, and import preflight\" icon=\"cube\" \u003e}}\n {{\u003c card link=\"./agent-definitions/\" title=\"Agent definitions\" subtitle=\"How .agent.yaml files declare runnable agents and bindings\" icon=\"user\" \u003e}}\n {{\u003c card link=\"./capabilities-and-prompts/\" title=\"Capabilities and prompts\" subtitle=\"How annotated Markdown becomes reusable agent behavior\" icon=\"speakerphone\" \u003e}}\n{{\u003c /cards \u003e}}","description":"How pack source directories, agent definitions, capabilities, prompts, archives, and imports fit together.","title":"How packs work"}
Once you know what comes in the built-in packs, use these pages to understand the underlying architecture: how source files become importable archives, how .agent.yaml definitions bind agents to behavior, and how annotated Markdown becomes reusable capabilities and prompts.