Menu
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
| name | grill-me |
| description | Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions. |
Existing docs first. Root CONTEXT-MAP.md lists contexts.
Single-context:
/
├── CONTEXT.md
├── docs/adr/
└── src/
Multi-context:
/
├── CONTEXT-MAP.md
├── docs/adr/ ← system-wide
├── .claude/CONTEXT.md ← AI tooling
├── .github/CONTEXT.md ← CI YAML
└── packages/
├── ordering/CONTEXT.md
└── billing/CONTEXT.md
Contexts go wherever a coherent vocabulary lives — packages, plus non-source dirs (.claude/, .github/). Narrowest scope owning the term.
Create lazily. First new context in a single-context repo → also create CONTEXT-MAP.md; move existing root CONTEXT.md to its proper scope if it doesn't belong at root.
CONTEXT.md inline as terms resolve. Don't batch. Format: CONTEXT-FORMAT.md. Glossary only — no specs/scratch/decisions.writing, running, and debugging Playwright tests; creating and recreating scratch orgs (Dreamhouse, minimal, non-tracking); working with their output from github actions
Guidelines for consuming salesforcedx-vscode-services extension API. Use when working with extensions that have extensionDependency on salesforcedx-vscode-services, registering commands, using Workspace/Connection/Project/Settings/FS/Channel/Media services, quickpick/quickInput, implementing file/config watchers, editing extensionProvider.ts, buildAllServicesLayer, AllServicesLayer, setAllServicesLayer, prebuiltServicesDependencies, or Layer composition for VS Code extensions.
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Interact with the Gus Salesforce org via CLI (sf). Query, create, update work items; query team epics. Use when user mentions Gus, work items, epics, or GUS/Git2Gus workflows.
Verification steps for code changes. Use after ANY code change to ensure quality, or when creating plans because those should include verification steps.
Polish the automated CHANGELOG for a release branch. Removes GUS refs, categorizes under-the-cover changes, improves customer-facing descriptions. Use when preparing/reviewing the changelog on a release branch, or when user mentions changelog quality.