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 when changing brand canon or when the task is ambiguous; otherwise load only the matching task reference below.

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 and marketing surfaces. Headings, nav, button labels, post titles, file names that show in UI, the studio name. Always on uinaf-controlled product and marketing surfaces. Documentation surfaces (README.md, CHANGELOG.md, product docs pages, docs/*.md, CONTRIBUTING.md, SECURITY.md, AGENTS.md, CLAUDE.md, GitHub templates) use proper-case headlines and sentence-case body; see references/repo-docs.md for repo docs.
• 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. UI fills, gradients, and default text stay neutral.

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