with one click
typescript
TypeScript coding standards and conventions including file naming rules
Menu
TypeScript coding standards and conventions including file naming rules
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.
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.
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.
| name | typescript |
| description | TypeScript coding standards and conventions including file naming rules |
Copyright (c) 2026, salesforce.com, inc.)as Foo or as unknown as or Foo!). do guards or Effect.schema stuff (ex is) insteadvoid for async - use async/effect (exception vscode-window-messages)export * - name exports explicitlyundefined over null (unless server requires null)undefined over empty stringany