maskin-design
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
The v2 Maskin app design system — tokens, type, radii, shadows, motion, and component patterns extracted from the full Maskin App v2 prototype (all fourteen product screens plus the shell and overlays). Use this when designing or building any product route, when reviewing a screen against v2, or when generating brand-consistent artefacts.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-shadcn-componentSkill
- frontend-taskSkill
- workspace-observer-onboardingSkill
- add-shadcn-componentSkill
- frontend-taskSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Read readme.md first — it names the source, what the v2 rebuild changed, and where the truth lives.
- Very specific: line 16
When building throwaway prototypes or slides, copy the tokens from tokens/ and load the same two families listed in tokens/fonts.css …
- Very specific: line 18
When touching production code, apps/web/src/app.css already carries the v2 palette + radii + shadows and self-hosts the fonts under …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read readme.md first — it names the source, what the v2 rebuild changed, and where the truth lives.
The mockup file has two forms in this folder:
maskin-app-v2.html— the self-contained bundle. Open this in a browser to walk the mockup — it renders the whole app as it actually behaves (sidebar, top nav, every screen, menus, modals, overlays).maskin-app-v2.dc.html+support.js— the extracted.dcmarkup and its runtime. Does not render standalone (open the bundle above for that). Use it to jump straight to a component's markup by line number, using the map inMOCKUP-INDEX.md.
The v2 mockup covers all fourteen product screens — For you, Chats, Objects, Object detail, Loops, Trigger detail, Loop detail, New loop, Agents, Agent detail, Search, Marketplace, Marketplace detail, Settings — plus the sidebar/icon rail, the shared top nav, the command palette and create picker, the Stripe checkout and the edit-instructions modal. MOCKUP-INDEX.md maps every screen to its line range and its owning route. Build a screen against its own section; do not extrapolate from another one.
When building throwaway prototypes or slides, copy the tokens from tokens/ and load the same two families listed in tokens/fonts.css (Schibsted Grotesk + JetBrains Mono).
When touching production code, apps/web/src/app.css already carries the v2 palette + radii + shadows and self-hosts the fonts under apps/web/public/fonts/. Go through the semantic classes (bg-background, text-foreground, border-border, bg-brand, .eyebrow) rather than importing this skill's CSS.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

