# Agentic Development for .NET GraphQL

> Build with agents on a platform designed for agentic development. Skills, .NET patterns, schema checks, and MCP keep humans and agents aligned.

Canonical source: https://chillicream.com/platform/agentic-coding

Agentic development

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.

`$ dnx skills add chillicream/agent-skills`

One command teaches your agent the platform.

Agent directory

## Bring the agent you already use.

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.

- ![](https://chillicream.com/agent-logos/claude.svg)Claude
- ![](https://chillicream.com/agent-logos/codex.svg)Codex
- ![](https://chillicream.com/agent-logos/copilot.svg)Copilot
- ![](https://chillicream.com/agent-logos/cursor.svg)Cursor
- ![](https://chillicream.com/agent-logos/windsurf.svg)Windsurf
- ![](https://chillicream.com/agent-logos/gemini.svg)Gemini
- ![](https://chillicream.com/agent-logos/cline.svg)Cline
- and many more

Review

## Review stays fast because changes stay uniform.

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.

feat: add product reviews3 files changed+73 \-2In Review

Reviews/AddReview.cs+34\-2Viewed

+\[Mutation\]

+static Task<Review> AddReviewAsync(...)

Reviews/ReviewAddedHandler.cs+21\-0Viewed

+class ReviewAddedHandler : IEventHandler<ReviewAdded>

+ValueTask HandleAsync(ReviewAdded e, ...)

Reviews/GetSummaryHandler.cs+18\-0Viewed

+class GetSummaryHandler : IQueryHandler<GetSummary, Summary>

+ValueTask<Summary> HandleAsync(...)

Checks

- BuildIn progress
- TestsIn progress
- Schema ChecksIn progress

Approve

review effort

uniform changes, faster reviews

Skills

## Skills give your agent a head start.

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

### graphql-schema-design

Schema design and review.

Proposes SDL in design mode and audits schema diffs in review mode, following the team's conventions.

`$ dnx skills add chillicream/agent-skills --skill graphql-schema-design`

SKILL.md

### prototype-feature

Frontend prototype with mock data.

Builds a clickable, local-only prototype with realistic mock data before any schema or backend work.

`$ dnx skills add chillicream/agent-skills --skill prototype-feature`

SKILL.md

### prototype-to-contract

Prototype to backend contract.

Turns an accepted prototype into colocated GraphQL fragments and a contract for the backend.

`$ dnx skills add chillicream/agent-skills --skill prototype-to-contract`

[Browse chillicream/agent-skills](https://github.com/chillicream/agent-skills) [Read the skills docs](https://chillicream.com/docs/skills)

Patterns

## One pattern per problem.

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`[Query]`

Mutation`[Mutation]`

DataLoader`[DataLoader]`

Pagination`[UseConnection]`

Authorization`[Authorize]`

Filtering`[UseFiltering]`

Event handler`IEventHandler`

Request handler`IEventRequestHandler`

Feedback

## Feedback before the merge.

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.

agent patchremove Product.price

published opsProductCard { id name price }

feedbackbreaking: published clients affected

agent fixdeprecate Product.price instead

[Explore GraphQL schema checks](https://chillicream.com/platform/release-safety)

At runtime

## Your API is a tool, too.

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`.

[Read the MCP adapter docs](https://chillicream.com/docs/hotchocolate/adapters/mcp)

Tool exposure

getProductidempotent

searchOrdersidempotent

createReviewdestructive

## Point your agent at the platform.

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.

`$ dnx skills add chillicream/agent-skills`