the studio floor
80 skill directories ship inside the plugin — every one a written procedure with its own triggers, rules and worked example. Enumerable proof beats adjectives, so the whole roster is below and you can filter it.
the index
One line per skill, transcribed from the plugin's ROSTER.md. Filter as you type — the URL keeps your query, so a filtered view is a link. ⌘K lands here too.
80 of 80 skills
the root pipeline itself
1
the design constitution and cross-cutting judgment
5
defines the brief, direction, sitemap, and voice
7
tokens for color, type, layout, depth, shape, and motion
11
the UI component library, section by section
18
motion, scroll, transitions, and interactive set pieces
8
App Router structure, routing, data, and SEO
10
APIs, database, auth, email, payments, and consent
9
empirical checks: code, responsive, visual, a11y, perf
7
preview, deploy, and handoff to production
4
the specialists
Opus 5
The adversarial critic. It scores screenshots against the committed direction and the taste constitution, and it is under no obligation to be nice about either.
scores screenshots against DIRECTION.md + taste rubric; returns ranked defects · used by gate-visual to judge design quality
Sonnet 5
Sweeps every breakpoint with a real browser and reports what it actually saw — not what the markup implies.
used by gate-responsive and gate-visual for empirical browser QA
Opus 5
Repairs a broken toolchain without the classic cowardice of downgrading the stack until the error goes away.
used whenever scaffold or gate-code hits tooling failures
Routing is deliberate: judgment stays on the lead model, specialist builds and critiques run on Opus 5, mechanical sweeps run on Sonnet 5.
The gates they report towrite-time enforcement
The plugin registers a PostToolUse hook. hooks/antislop.sh reads every Write and Edit, greps it against the banned list in roughly thirty milliseconds, and blocks the ones that fail — slop never reaches the file. Its sibling studio-log.sh feeds the /studio activity feed.
this session
Not just a capability statement — a receipt. During this build the anti-slop hook fired and blocked a real write (the one licensed surface that quotes the banned list), and studio-log.sh recorded every agent this session launched. The build briefly believed otherwise — its probe had tested a file the hook is scoped to ignore — and the correction is in the paper trail.
the recurring cast
Nearly every skill closes with a worked example, and the examples share a cast. Their palettes, routes and signature moves are fixed in CAST.md, so two skills that touch the same client still agree with each other three hours apart. All eight are invented.
None of them run until the interview and your approvals say so.