Skills

28 specialists for the engineering work around vibe coding.

Twenty-eight research-backed specialists for the work between “I have an idea” and “it is live in production.” Each skill owns one job, carries its own restraints and verification contract, and loads only when it is relevant.

Each package has a workflow and verification contract. The current upgrade repairs demonstrated gaps; cross-runtime behavior and comparative outcomes remain empirical questions. See the 28-row upgrade ledger.

npx skills add udaysharmadev/Skills --all

Try a direct request such as “Use sleuth to find why this value stays stale after a write.” You should receive a reproduction, a causal explanation, a scoped fix and its check output. /concierge is optional when the owner is unclear.

Building one feature, fixing one bug, or cleaning one frightening repo: you do not need to memorize 28 commands. Use the owner you know, or ask concierge.

From idea to production

flowchart LR
    A["IDEAhotseat"] --> U["UNDERSTANDspelunk"]
    U --> R["RESEARCHscout"]
    R --> S["SPECdistill"]
    S --> P["PLANmasterplan"]
    P --> B["BUILDpilot · backend"]
    B --> D["DESIGNpolish · friction · ditto"]
    D --> V["PROVEproof · roadtest · referee"]
    V --> C["CLEANunslop · janitor · frugal"]
    C --> H["SHIPcleared · runway"]
    H --> M["REMEMBERrecall"]
    B -. "architecture" .-> X["blueprint · headroom"]
    V -. "diagnose" .-> Y["sleuth · hotpath · harden"]

This is a map, not a mandatory chain. Most requests need one skill. Larger workflows compose only where the next specialist needs the previous one’s output.

Why this is different

Research-backed depth

Every skill received an individual research pass. Its provenance note records the lessons that changed behavior, where those lessons were encoded, rejected ideas, and knowledge that should be refreshed as the field moves. The research index keeps that evidence browseable without putting it into runtime context.

Specialist judgment

These are not “act like an expert” prompts.

• sleuth keeps competing hypotheses alive until an experiment separates them.
• headroom attaches a trigger metric to every scaling recommendation, and tells you what not to build yet.
• harden separates severity, confidence, exploit preconditions, and impact.
• unslop protects load-bearing weirdness instead of rewriting everything clean.
• frugal optimizes successful-task token cost, never raw token count.
• runway verifies the deployed fingerprint through the public URL, not the