一键在 Manus 中运行任何 Skill

packagejson

星标1,024

分支454

更新时间2026年6月30日 14:09

package.json conventions for this repo. Use when editing/reviewing a package.json — name, types, browser, files, dependencies, devDependencies, packaging, scripts, or vscode contributes.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

forcedotcom

forcedotcom/salesforcedx-vscode

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

SKILL.md

readonly

name	packageJson
description	package.json conventions for this repo. Use when editing/reviewing a package.json — name, types, browser, files, dependencies, devDependencies, packaging, scripts, or vscode contributes.

name

non-npm package → @salesforce/foo (whether published or not)
vscode-extension package → salesforcedx-vscode-foo
don't rename; flag mismatches to the user

types

extension: needed only if it's an extensionDependency of another extension
non-extension package: not needed

browser

web-enabled extensions only; must point to a bundled dist file

files

packages that publish to npm need a files prop

scripts

See wireit skill

dependencies

another package in this repo → version *
no dependency on salesforcedx-vscode-services (extensionDependency / devDependency ok)

devDependencies

don't duplicate devDependencies already at repo top level

packaging

legacy vsce script (mutates pjson at package time); don't create new ones, want them gone

vscode "contributes"

tips

commands show in command palette by default; suppress via never/when under commandPalette
commands need a unique ID; 2 extensions with the same config → UI warning
never a default:true boolean config (hard to override user/workspace)

ESLint rules

Rules from @salesforce/eslint-plugin-vscode-extensions (packages/eslint-local-rules; published to npm) enforce good package.json:

package-json-i18n-descriptions: Requires %key% placeholders (not hardcoded strings) in commands, config, debuggers, views, walkthroughs. Validates keys exist in package.nls.json
package-json-extension-icon: Published VS Code extensions (salesforcedx-vscode*) must have top-level icon; icon path must exist when specified
package-json-icon-paths: Validates commands[*].icon and viewsContainers.activitybar[*].icon have both light/dark and files exist
package-json-command-refs: Menu commands must reference defined commands; reports orphaned commands
package-json-view-refs: View IDs must be referenced in menu when clauses or viewsWelcome; reports orphaned views

同仓库更多 Skills

同仓库

effect-best-practices

forcedotcom/salesforcedx-vscode

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.

2026-07-011.0k

services-extension-consumption

forcedotcom/salesforcedx-vscode

Consume the salesforcedx-vscode-services extension API. Use when an extension depends on salesforcedx-vscode-services and you are registering commands, calling its services (Workspace, Connection, Project, Settings, FS, Channel, Media, prompts), watching files/config/target-org, or wiring the AllServicesLayer/runtime in extensionProvider.ts.

2026-07-011.0k

paths

forcedotcom/salesforcedx-vscode

Prefer vscode-uri over node:path. Use when .ts files in /src import node:path or use path.join/basename/dirname/resolve, URI.file, or memfs paths.

2026-06-301.0k

icons-src

forcedotcom/salesforcedx-vscode

Add custom SVG icons to salesforcedx-vscode-services for font generation. Use when adding new icons to media/icons-src, creating SVG icons for VS Code extension, or defining font-based icons.

2026-06-301.0k

typescript

forcedotcom/salesforcedx-vscode

TypeScript coding standards — apply when writing, reviewing, or refactoring .ts/.tsx, or naming/renaming .ts files (camelCase casing).

2026-06-301.0k

gus-cli

forcedotcom/salesforcedx-vscode

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.

2026-06-291.0k

name	packageJson
description	package.json conventions for this repo. Use when editing/reviewing a package.json — name, types, browser, files, dependencies, devDependencies, packaging, scripts, or vscode contributes.

name

non-npm package → @salesforce/foo (whether published or not)
vscode-extension package → salesforcedx-vscode-foo
don't rename; flag mismatches to the user

types

extension: needed only if it's an extensionDependency of another extension
non-extension package: not needed

browser

web-enabled extensions only; must point to a bundled dist file

files

packages that publish to npm need a files prop

scripts

See wireit skill

dependencies

another package in this repo → version *
no dependency on salesforcedx-vscode-services (extensionDependency / devDependency ok)

devDependencies

don't duplicate devDependencies already at repo top level

packaging

legacy vsce script (mutates pjson at package time); don't create new ones, want them gone

vscode "contributes"

tips

commands show in command palette by default; suppress via never/when under commandPalette
commands need a unique ID; 2 extensions with the same config → UI warning
never a default:true boolean config (hard to override user/workspace)

ESLint rules

Rules from @salesforce/eslint-plugin-vscode-extensions (packages/eslint-local-rules; published to npm) enforce good package.json:

package-json-i18n-descriptions: Requires %key% placeholders (not hardcoded strings) in commands, config, debuggers, views, walkthroughs. Validates keys exist in package.nls.json
package-json-extension-icon: Published VS Code extensions (salesforcedx-vscode*) must have top-level icon; icon path must exist when specified
package-json-icon-paths: Validates commands[*].icon and viewsContainers.activitybar[*].icon have both light/dark and files exist
package-json-command-refs: Menu commands must reference defined commands; reports orphaned commands
package-json-view-refs: View IDs must be referenced in menu when clauses or viewsWelcome; reports orphaned views