agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/packageJson/SKILL.md

packageJson

Skill1k starsChanged 26 days agoBSD-3-ClauseView on GitHub

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

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    don't rename; flag mismatches to the user

    line 11
  2. Very specific:

    no dependency on salesforcedx-vscode-services (extensionDependency / devDependency ok)

    line 33
  3. Distinctive:

    don't duplicate devDependencies already at repo top level

    line 37
  4. Very specific:

    never a default:true boolean config (hard to override user/workspace)

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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
  • command titles (%key% → package.nls.json), menus, notification slots: command-ui
  • 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free