ChilliCream
- 13 skills
- 0 followers
- 6 hours ago last updated
- ▌ GRAPHQL Schema Design · chillicream bundleGraphQL schema design and review. Use when designing new GraphQL schema changes (types, mutations, queries, connections, enums, errors), reviewing schema diffs, planning schema evolution, or auditing nullability and naming. Triggers on 'graphql schema design', 'design a mutation', 'design a query', 'design a type', 'new type', 'new mutation', 'review schema', 'review schema diff', 'schema review', 'schema evolution', 'audit the schema', '/graphql-schema-design'.
- ▌ Prototype To Contract · chillicreamConvert a local-only prototype into Relay-backed component fragments and a schemaExtensions backend contract. Use when mock data and local action hooks must become route queries, colocated fragments, and read/write GraphQL specs. Trigger on "prototype to contract", "mock to contract", "turn this prototype into a contract", "fragmentize this page", "wire this mocked page to GraphQL", or "spec this feature for the backend". Do not use for isolated fragment cleanup or schema design without a prototype UI.
- ▌ Nitro Task Orchestrator · chillicream bundleDrive a nitro agent tasks backlog to completion as the orchestrator; waves of subagents grouped by code area, every task reviewed before it closes. Use when the user says 'orchestrate the backlog', 'run the wave pipeline', or wants many tasks implemented autonomously. Not for single small changes.
- ▌ Hotchocolate Best Practices · chillicream bundleHotChocolate 16.6+ server implementation best practices for .NET GraphQL services. Use when writing or reviewing C# in a HotChocolate project — resolvers, classes with [QueryType], [MutationType], [ObjectType], or [DataLoader], Green Donut DataLoaders, EF Core data access inside resolvers, pagination, or GraphQL performance work in .NET. Triggers on 'HotChocolate', 'Green Donut', 'DataLoader', 'resolver', 'AddGraphQLServer', or any edit to a file that uses HotChocolate attributes or types. Applies to standalone servers and to source schemas (subgraphs) in a composite setup.
- ▌ Nitro Mail · chillicreamSend and receive mail between coding agents with `nitro agent mail`: local-first, per-workspace messaging for multi-agent coordination. Use when messaging or replying to another agent, draining an inbox, or waiting for new mail.
- ▌ Nitro Task · chillicreamCreate and manage tasks with `nitro agent tasks`, the local-first, dependency-aware issue tracker for coding agents. Use when creating or triaging tasks, wiring dependencies, finding ready work, or updating and closing what you worked on.
- ▌ Nitro Memory · chillicreamSave and recall shared, durable agent memory with `nitro agent memory`: knowledge that must outlive the session -- preferences, decisions, domain facts, references -- readable by every agent in the workspace. Use when the user says "remember this", when a session should start from what the workspace already knows, or when knowledge worth keeping surfaces mid-task.
- ▌ Nitro Research · chillicream bundleAnswer a question with cited evidence from primary sources (official docs, source code, specs, first-party APIs). Use when the user says "research", or when a decision or plan waits on a fact from outside the working directory. Not for facts in the current codebase; grep for those.
- ▌ Nitro Wayfinder · chillicream bundlePlan a large, fuzzy feature as a shared map of decision tickets in nitro agent tasks, resolve them one per session until the way is clear, then cut the implementation-ready task graph. Use when the user says "wayfind", "chart a map", "work the map", "next decision", "plan this like a map", invokes /nitro-wayfinder, or brings an effort too big and foggy for one agent session. Not for work that fits one session; create tasks with nitro agent tasks directly for that (see the nitro-task skill).
- ▌ Prototype Feature · chillicreamBuild a clickable local-only frontend prototype from a plain-English feature request, with realistic mock data and action hooks shaped for later GraphQL mutations. Use when the user asks to prototype, mock up, wireframe, sketch, or build UI before backend/schema work exists ("no backend yet", "no GraphQL yet", "just the UI"). Do not use when wiring a real backend or designing the GraphQL contract now.
- ▌ Nitro Task Planner · chillicreamSecond half of nitro-task-orchestrator. Run a planning session that turns feedback, goals, or feature briefs into well-formed nitro agent tasks and hands the work to the orchestrator over nitro agent mail. Use when the user says 'plan the backlog', 'act as planner', 'turn this feedback into tasks', or 'plan tickets for the orchestrator'. Not for implementing or closing tasks.
- ▌ Skill Author · chillicream bundleAuthoring guide and conventions for ChilliCream agent skills. Use whenever the user wants to create a new skill, edit an existing one, improve a skill's description, or asks how to structure a SKILL.md file. Triggers on phrases like "write a skill", "new skill", "author a skill", "improve this skill", "skill description", "SKILL.md", or when editing any file under skills/*/SKILL.md or .claude/skills/*/SKILL.md.
- ▌ Hotchocolate Fix Bug · chillicreamUse when the user wants a reported HotChocolate bug triaged, reproduced, and fixed from a GitHub issue, working in the ChilliCream graphql-platform repository. N stands for an issue number throughout. Triggers on: 'fix bug', 'fix this bug', 'fix issue #N', 'fix #N', 'is issue #N a bug', 'triage issue #N', 'reproduce and fix', 'look into this issue', pasted issue URL or report asking whether it is a real bug. Do NOT use for feature requests, plain code review, or questions about how an API works that reference no reported defect.