Small asks get the light touch — the right-sized response, every time.
a dance-studio SaaS · routine ops — no skill needed
$ “can you pull from remote? the client put a doc there”
The work runs through
Recognized as mechanical git work and handled directly — no skill fired, no ceremony. The classifier knows when to stay out of the way.
an agency CRM · an explain question
$ “explain this ID-constants file properly — this is where the drift happens”
Force-read before the turn
The work runs through
/composure:app-architectureThe lighter skill, not a full blueprint — a single-file convention question answered from the catalog, drift documented at its source.
a café site · a fix-it ask
$ “read how we do interfaces in the catalog — the site navigation config still isn't set up right”
Force-read before the turn
The work runs through
/composure:app-architectureFound three duplicate type families, a circular import, and four dead auth links — all fixed against the catalog shape, build- and render-verified in the same loop.
Every walkthrough traces to a real session in the archive — prompts paraphrased, project flavors generalized, no client specifics. Where a skill had no real moment to show, it isn't shown.