chillicream-skills

Plugin chillicream-skills from marketplace chillicream-agent-skills in ChilliCream/agent-skills. Commands read from the repo's manifest — 10 days ago.

Skills (14)

• skill-author

  Authoring 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

• bdd-best-practices

  BDD best practices for writing, reviewing and refactoring Gherkin scenarios, feature files and step phrases, with 31 numbered rules and webshop examples. Use when working on .feature files, checking whether a scenario follows BDD best practices, or discussing a rule by number ("breaks rule 13").

• graphql-schema-design

  GraphQL 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',

• hotchocolate-best-practices

  HotChocolate 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, paginatio

• hotchocolate-fix-bug

  Use 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 issu

• nitro-mail

  Send 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-memory

  Save 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

• nitro-research

  Answer 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-task-orchestrator

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

• nitro-task-planner

  Second 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',

• nitro-task

  Create 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-wayfinder

  Plan 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 /

• prototype-feature

  Build 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 Gr

• prototype-to-contract

  Convert 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 pro