Menu
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
| name | architecture-patterns |
| description | System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations. |
| allowed-tools | Read, Write, Edit, Bash, Grep, Glob, WebSearch |
Guidance for system architecture and API design decisions within CC10X workflows. Used during PLAN and BUILD workflows for architectural choices.
Architectural decisions require user approval when:
planner (architecture planning)component-builder (architecture implementation)code-reviewer (architecture review)Orchestrate complex, multi-step AI workflows with quality convergence loops, event-sourced state, and human-in-the-loop approval gates. Use when the user wants to babysit a task, orchestrate a workflow, run quality-gated development, resume a previous orchestration run, diagnose run health, plan without executing, set up a project or user profile for babysitter, or assimilate an external methodology. Also use when the user mentions "babysitter", "orchestrate", "babysit", "quality loop", or "convergence loop".
Help and documentation for babysitter commands, processes, skills, agents, and methodologies.
Plan a babysitter workflow without executing it. Focus on creating the best process possible.
Install or refresh a team-pinned babysitter runtime/content setup from lockfile.
Start a babysitter orchestration run. Use this command to start babysitting a complex workflow.
Analyze a completed or in-flight run and propose process improvements for future runs.