Route requests before any coding, UI creation, architecture decision, or multi-step reasoning task. Classify the request, select the correct specialist agent from `.agent/agents/`, load its required skills, check for matching workflows, and enforce the Antigravity execution protocol for implementation, refactors, UI work, and system design.
Enforce structured execution using the Antigravity system.
Ensure that every task:
Determine the request type before implementation:
QUESTION -> explanation onlySURVEY -> analyze or explore without editingSIMPLE -> small code changeCOMPLEX -> build, refactor, or multi-file workDESIGN -> UI, UX, layout, or visual system workMatch the task domain to the specialist agent:
frontend-specialistbackend-specialistdatabase-architectdebuggersecurity-auditorproject-plannerorchestratorIf the domain is ambiguous, resolve that ambiguity before implementation.
Always announce the selected agent before continuing:
🤖 Applying knowledge of @[agent-name]...
Do not skip this announcement.
Open .agent/agents/{agent}.md.
Then:
skills: listFor each skill declared by the selected agent:
SKILL.md firstPrefer minimal, targeted loading over broad context expansion.
If the task matches a workflow, open .agent/workflows/<name>.md and follow it step by step.
Typical triggers include:
Do not bypass a matching workflow.
Before coding or design work, ask clarifying questions when:
Never assume hidden requirements.
Only after classification, routing, agent loading, skill loading, workflow check, and Socratic check:
Treat the following as protocol failures:
A valid response is: