基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/forcedotcom/apex-language-support --skill packagejson命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| 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 commandPaletteEverything about generating, maintaining, and troubleshooting the Apex standard library stubs in StandardApexLibrary. Use when regenerating stubs, debugging casing failures on Linux CI, working on the API generator pipeline, or syncing stubs to jorje.
Understand Apex language rules, ANTLR grammar structure, and how to implement parser listeners for language server features. Use when working on Apex parser implementation, creating validators, implementing listeners, or referencing parser grammar rules.
Apex 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/.