Repository workflow

A catalog you can rebuild.

The interface reads the same inventory you review in Git. Update the source once; the catalog follows.

Source of truth

skills.json holds metadata. guides/ holds judgment.

Skills to type

/pick-skillsAny repository
Names the installed skills that fit a task, as a phase-by-phase plan. It reads the guides and stops; it never runs the work.
/find-skillsAny repository
Searches for a capability nothing installed covers yet, rather than choosing among the skills you already have.
/add-skillThis repository
Registers a skill you just installed, and decides where it belongs.
/update-skillsThis repository
Brings tracked skills up to date, then re-checks the guide entries of the ones that changed.

None of them can start the skill they recommend. Most skills here are user-invoked, so a plan naming one is a prompt for you to type it.

01
pnpm scan
Regenerate the inventory after installing, modifying, or removing a skill.
02
guides/<category>.md
Reference the skill in exactly one guide. Write when to pick it and when not to.
03
pnpm verify
Guide coverage, TypeScript, tests, and the production build.

01
pnpm updates
See what drifted upstream. Exit status 2 means updates were found, not that something failed.
02
pnpm reinstall --apply
Restore tracked sources. Locally modified skills are skipped unless you opt in.
03
pnpm scan && pnpm verify
Refresh the catalog, then re-read the guide entry of every skill that changed.