ctx

Define or update architectural patterns, boundaries, and layers. Triggers on "architecture", "patterns", "layers", "hexagonal", "clean architecture", "module boundaries", "API design", "system design". Use when discussing code organization or technical structure. For technology choices, use /ctx:techstack instead.

Decompose an epic or investigation into actionable task files in .context/tasks/. Triggers on "break down", "decompose", "create tasks from", "split into tasks", "breakdown". Use when an epic or investigation is ready and needs concrete work items. For standalone tasks without an epic, use /ctx:create-task.

Initialize or check the .context/ folder structure for task tracking. Triggers on "init context", "setup context", "create .context", "initialize project tracking". Use when .context/ folder is missing or needs verification. For full project setup, use /ctx:start instead.

Create a single task file from a brief description, independent of any epic. Triggers on "create task", "new task", "quick task", "add a task for", "I need to fix/add/update X". Use for one-off tasks, bug fixes, or small work that doesn't warrant a full epic. For epic-based tasks, use /ctx:breakdown.

Capture and maintain business logic, domain knowledge, flows, rules, and edge cases in plain text. Use when the project has business rules, user flows, domain concepts, or invariants that code alone cannot convey. Triggers on "domain", "business logic", "business rules", "flows", "domain model", or when discussing how a system behaves from a business perspective.