SKILL.md
graphql-schema-design
Schema design and review.
Proposes SDL in design mode and audits schema diffs in review mode, following the team's conventions.
Agents are strong at filling a known pattern and weak at inventing architecture. The platform gives your agent the pattern to fill, your conventions as checked-in skills, and feedback it can act on before the merge, so what comes back is best-practice code.
One command teaches your agent the platform.
Agent directory
Skills teaches supported agents the same conventions. MCP gives compatible agents access to your API. Switch agents without switching architectures, review standards, or your definition of good code.
Review
When agents fill the same patterns, changes come back in a familiar shape. Review stays a glance instead of an architectural investigation. Writing code is cheap now; reviewing it is where your time actually goes.
Checks
review effort
uniform changes, faster reviews
Skills
Prototype a feature, derive the contract, evolve the schema: on this platform those are workflows an agent can run, not rituals a developer performs. Skills package that working knowledge so agents start productive, and your own conventions ship the same way, reviewed like code.
SKILL.md
Schema design and review.
Proposes SDL in design mode and audits schema diffs in review mode, following the team's conventions.
SKILL.md
Frontend prototype with mock data.
Builds a clickable, local-only prototype with realistic mock data before any schema or backend work.
SKILL.md
Prototype to backend contract.
Turns an accepted prototype into colocated GraphQL fragments and a contract for the backend.
Patterns
Attributes mark queries, mutations, DataLoaders, and pagination; event handlers implement a single interface. The agent fills a known shape instead of inventing structure, so two features written weeks apart come back looking the same.
[Query][Mutation][DataLoader][UseConnection][Authorize][UseFiltering]IEventHandlerIEventRequestHandlerFeedback
Strong types turn many bad edits into compile errors. nitro checks schema changes in CI against the client registry, so a risky change comes back as feedback while the agent can still fix it.
At runtime
Host the MCP transport with AddMcp() and MapGraphQLMcp(). Supply tool definitions through Nitro or a custom IMcpStorage. MCP-compatible agents can then call those operation tools at /graphql/mcp.
Tool exposure
The patterns, the feedback, and the checks give every agent the same rails. One command installs ChilliCream’s skills; your own conventions ship the same way.