uinaf design system

Apply uinaf's identity to any creative output that ships under the studio name. Web is the most-supported track, but the same voice, type, and visual rules carry across content, slides, social, email, terminal, and native surfaces.

The canonical brand spec is references/brand-spec.md. Read it before producing anything new — it is the upstream source for every other reference in this skill.

Hard rules — universal (apply to every uinaf output)

• Berkeley Mono is the only typeface. No serifs, no sans, no second face. Off-uinaf fallback: JetBrains Mono.
• Lowercase voice on product surfaces. Headings, nav, button labels, post titles, changelog entries, file names that show in UI, the studio name. Always — on uinaf-controlled surfaces. Repo collaboration docs (README.md, CONTRIBUTING.md, SECURITY.md, AGENTS.md, CLAUDE.md, GitHub templates) are carved out and use proper-case headlines; see references/repo-docs.md.
• No emoji. Anywhere. Brand artwork is the only flair.
• Voice is short, direct, dry. No SaaS sludge ("empower", "unlock", "synergies"). Sentence fragments end with periods. This applies everywhere, including repo docs.
• Illustrations live on pure black with no chrome. The slime palette (lime / green / cyan / blue / purple / magenta / pink) stays inside artwork, terminal output, and rare data-viz — never as button fills, gradient washes, or default text.

Hard rules — UI surfaces (web, slides, native, email HTML)

• Square corners. Cap radius at 6px; 2px is the norm. Status dots are the only pill.
• No coloured CTAs. UI is monochrome neutrals. Hierarchy comes from weight and box position, not fill color.
• No shadows on UI. Borders do all the elevation work.