modes

You can guide UI, API, and integration tasks by referencing mode YAML files like ui.yaml or api.yaml. These files provide mode-specific guidance that automatically activates best-practice patterns based on the current work context to ensure safer, faster development.

Domain-mode playbooks are structured YAML definitions providing mode-specific guidance for UI, API, DB, and integration tasks. They enforce frontmatter metadata, mode definitions, and lifecycle hooks to drive behavior, governance, and documentation across multi-agent contexts.

You enforce governance and consistency through inheritance and composition of core skills. The system uses frontmatter metadata, mode YAML definitions, and lifecycle hooks to drive behavior and ensure consistent governance across all domain-specific development tasks.

Yes, mode YAML definitions support security and performance tasks through dedicated files like security.yaml and performance.yaml. These provide specialized guidance and per-mode checklists that automatically activate based on the specific development work being performed.

Automatic activation is set up by leveraging mode YAML definitions within the skills/modes directory. The system detects the work context and automatically selects and applies the appropriate mode guidelines, ensuring agents follow the correct patterns for each specific task.