studio
the house practice for design and front-end product work: the rules, the path through a session, what each tool is trusted for, and the tool mechanics that were paid for. one package for every project. every file it points to is in this folder; other skills are named, never linked by path.
what to read
paths are relative to this skill's folder.
- every session:
rules.md(the law), thenplaybook.md(the path for this kind of session). - before the first call to a tool: its practices file.
practices/paper.md: the paper canvaspractices/figma.md: figma, figjam, and the figma mcppractices/print-and-assets.md: image processing, pdf and print outputpractices/front-end.md: building, serving, and verifying front-end code
- when the session needs it:
doctrine/component-intake.md: turning an idea or reference into a componentdoctrine/codebase-scaffold.md: starting a codebase or changing its structuredoctrine/enforcement.md: wiring the prebuild gate (scripts/preflight.ts), declaring a project'sdesign.config.ts, or judging a boundary violationdoctrine/tool-intake.md: when the operator brings in a new tool, system, library, or guide to evaluateinventory.md: before reaching for any other skill, mcp, tool, library, font, or reference. it is the one index, including the route to the operator's saved resources
- emitting or inheriting a design-system package: use the
asbuiltskill. it owns the package format.
the loop
- operator intent first. open no reference before the operator says what the thing should do and feel like.
- references give anatomy, never skin. shadcn, base ui, and mobbin supply slots, variant axes, state lists, and behavior floors. when unsure, delete it: if that breaks behavior or the api, it is structure, so take it; if it only changes look or feel, it is skin, and skin is ours.
- deliverables are state graphs, not happy frames. every state
(default, hover, focus, active, disabled, loading, empty, error) with
its transitions, and motion numbers from
rules.mdwritten in the margins. - second-use gate. nothing becomes a component until it recurs.
- suppliers never decide. other skills are catalogs, and
rules.mdwins every conflict. - decisions live in the artifact. never transcribe design decisions
into docs. when a mistake costs real time, add a row where
rules.mdsays to.