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.

Ir a la instalación

Repositorio: Polkadot-Community-Foundation/polkadot-desktop-community
Última actividad en el origen: 10 de junio de 2026 a las 20:28
Idioma detectado de SKILL.md: inglés
Estrellas: 4
Forks: 1

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

6 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

architecture

Use BEFORE writing or changing any non-trivial code in `src/` — new code, new/moved/renamed files, a new abstraction, extending behavior, or a refactor that relocates logic. The single entry point that decides what the change is and where it goes before any file path is generated. Skip only for trivial in-place edits within one existing file.

2026-06-17

code-placement

Use BEFORE `domain-development`/`feature-development` when the target layer (domain, aggregate, feature, widget, shared) is uncertain — multi-layer changes, new abstractions, promoting code out of a feature, or "where should this live?". Skip when the layer is obvious.

2026-06-10

domain-development

Use when working in `src/domains/`, introducing/extending a domain's public API (services, resources, hooks, repositories, schemas, README), modeling a user action in domain terms, event-storming domain seams, or deciding whether business logic belongs in a domain.

2026-06-10

Ver todos los de este repositorio

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.