check-dependency-capabilities

Use before writing any non-trivial utility, helper, algorithm, data transformation, or wrapper that an installed dependency might already provide. Symptoms — about to hand-roll debounce/merge/groupBy/retry, a stream operator, a validator, or a wrapper around a first-party host/SDK package whose API you don't have in context.

Jump to install

Repository: Polkadot-Community-Foundation/polkadot-desktop-community
Last source activity: June 10, 2026 at 20:28
Detected SKILL.md language: English
Stars: 4
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

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.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Polkadot-Community-Foundation/polkadot-desktop-community --skill check-dependency-capabilities

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Check Dependency Capabilities

Before hand-writing a utility/helper/wrapper, check whether an installed package already exports it. The index under index/ is generated from every dependency's .d.ts (the authoritative, version-matched API surface).

Steps

Ensure the index exists and is fresh. The index is gitignored, so on a fresh clone it won't exist yet. Run the generator if index/symbols.tsv is missing, if index/.manifest.json doesn't match current dependency versions, or if package.json/package-lock.json changed since the manifest:

node .claude/skills/check-dependency-capabilities/generate.mjs

It regenerates only changed packages (near-instant when nothing changed; full build only on first run).

Grep the symbol table for the capability — try the concept and likely names:

grep -iP '\t(function|const|type|class)\t' .claude/skills/check-dependency-capabilities/index/symbols.tsv | grep -i 'debounce'

Columns are symbol⇥kind⇥package⇥jsdoc-first-line. A hit means a package already provides it.

Read the matched package's signatures for exact usage (one scoped file, e.g.):

cat .claude/skills/check-dependency-capabilities/index/lodash-es.md

(Slug rule: drop a leading @, replace / with __ — @novasamatech/host-api → novasamatech__host-api.md.)

Decide. Use the existing export if it fits. Only if nothing matches, write new code — and say in one line what you searched and why nothing fit.

Maintenance

The index is gitignored (project-specific derived data) and regenerated incrementally by generate.mjs (driven by index/.manifest.json). Config (scope, dev deps) lives at the top of generate.mjs. The generator and its node:test suites are self-contained in this folder — no project wiring.