Menu
Guidelines for package.json files in packages
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | packageJson |
| description | Guidelines for package.json files in packages |
any package that's not an npm package should be named @salesforce/foo (whether it actually published to npm or not) the package that publishes the vscode extension is named apex-language-server-extension don't rename packages, but do tell the user when stuff doesn't match the rules
on an extension, you only need a types prop if your extension will be an extensionDependency of some other extension.
probably not necessary for non-extension packages.
only for web-enabled extensions. Must point to a bundled dist file
packages that publish to npm should have a files property in the package.json
See wireit skill
use * as the version for anything that's another package in this repo
packages should not duplicate devDependencies that exist at the top level of the repo.
commands will appear in command palette. If you don't want that, you have to never or use some when under commandPaletteApex Language Server data architecture — type sources, worker topology, and data ownership. Use when working on type resolution, worker communication, resource loading, hover, definition, diagnostics, or any code in apex-ls/src/server/ or apex-parser-ast/src/symbols/.
Numbering convention for ordering GUS work items within an epic. Numeric prefixes in Subject__c express sequencing (do X before Y) and parallelism. Use when planning an epic, when the user states a dependency between work items, or when asked what's unblocked/ready in an epic.
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.
Create feature branches for all work. Use when creating branches, checking out, or pushing. Prevents accidental push to main.
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.
writing, running, and debugging Playwright tests. working with their output from github actions