Interface Systems · Hybrid async + live
Interface Systems Studio
Token naming, spacing ladders, and component contracts that survive handoff to engineering.
520,000 KRW · 5 weeks · teams 2–12
Overview
Build a pragmatic interface system with naming that engineers adopt without a translation layer. Includes office hours on documentation tone and governance.
What is included
- Semantic token naming workbook
- Spacing and type ramps tuned for SaaS density
- Component contract worksheet (props, states, a11y)
- Storybook-ready annotation patterns
- Governance cadence for additions and deprecations
- Peer review scripts for system PRs
- Quality standards checklist for external reviewers
Outcomes
- A documented baseline kit for one surface area
- A merge checklist your design ops can own
- Three exemplar components with full state matrices
Jonah Ahn
Curriculum designer translating design ops rituals into cohort assignments.
FAQ
Is this only for greenfield systems?
No. Most teams retrofit; we start from an inventory of live components and deprecate in slices.
Limitations?
We do not implement production code. Engineers join critiques but coding is out of scope.
Tooling requirements?
Figma or Penpot for libraries; optional Storybook for engineers who want parity checks.
Participant notes
-
“The contract worksheet caught three ambiguous hover states before QA opened a single ticket.”
Helena · Ops analytics suite