← Atlas · Topics: design-md, agents-and-prompts, typography-and-styles
TypeUI
- Site
- typeui.sh
- Type
- style library
- Verdict
- Useful
- Licence
- Conditional licence, mixed
mixedthe CLI and the public GitHub registry (bergside/awesome-design-skills, 67 skills) are MIT. The website's own resources fall under a TypeUI EULA: Creative $30/month, Insights (beta) $30/month, All-access $50/month, with yearly billing and an AppSumo lifetime deal also offered. - Agent channels
- mcp, cli, skill
- Pricing
- freemium
- Reviewed
What it is
TypeUI is a platform from Bergside, the team behind Flowbite. It ships "design skills": each one is a visual direction written as a SKILL.md plus a DESIGN.md. The skills are named after styles, not brands (glassmorphism, neobrutalism, paper, editorial, claymorphism...). According to the site there are 94 design skills and 449 UI prompts. The paid tiers add UI animations, UI sound effects, brand kits, UI/UX audits and a separate analytics product.
When to open it
- When you want a generic look (say "brutalist" or "soft neumorphic") rather than a copy of a real company's style.
- When you want the agent to follow strict rules (component states, accessibility, quality gates) and not just a palette.
- When you want to create your own DESIGN.md through a guided CLI instead of writing one by hand.
Most useful
- The open registry: 67 style folders on GitHub, each with a
SKILL.mdfor agents and a shorterDESIGN.mdfor people. - The
DESIGN.mdformat: YAML front matter (name,colors,typography,rounded,spacing) followed by Overview, Style Foundations, and Colors. - The
SKILL.mdformat: Mission, Brand, Style Foundations, Accessibility, Writing Tone, Do and Don't rules, Expected Behavior, Required Output Structure, Component Rule Expectations, and Quality Gates. - Skill pages list the component families covered, the required states for each, and a WCAG 2.2 AA target.
- A separate
typeui-fundamentalsskill covers general UI/UX rules.
Using it with agents
- CLI:
npx typeui.sh pull <slug>fetches a registry skill (add--format designfor DESIGN.md, which is written to the project root).listbrowses the registry.generateandupdatebuild a file from interactive questions.randomizecreates a random starter system. - MCP: a hosted server at
https://mcp.typeui.sh/mcpwith OAuth sign-in. It serves skills, prompts and layout variations. You can publish your own workspace design system (from a theme, a markdown ZIP, or a Figma import in beta) as several markdown files that the MCP then serves. - There are setup guides for Codex, Claude, Cursor and about twenty other tools. Related extractors from the same team: TypeUI DESIGN.md Extractor, plus Figma and Penpot plugins.
Watch out for
- There are two licences. Registry files on GitHub are MIT. Anything copied, downloaded or reached over MCP from the website falls under the EULA. The EULA allows personal, client and commercial projects, and you keep the output after cancelling. It forbids redistributing the files or collections, or using them to build a competing registry or dataset. Account-gated resources may only be used while a paid plan is active.
- The registry
DESIGN.mdfiles are short and templated (about 55 lines). The detailed rules are inSKILL.md, so give the agent both files. - Everything is style-based, so no file captures a real brand. If you need a brand reference, look at Refero Styles or getdesign.md.
- The site sits behind a bot checkpoint, so plain
curlgets an HTTP 429. Use the GitHub registry for scripted access.
Reusable ideas
- Split the design spec in two: a strict agent-facing
SKILL.md(rules, states, quality gates) and a human-facingDESIGN.md(intent, rationale). - Add "quality gates" (acceptance checks a reviewer can test) to your own DESIGN.md, not just tokens.
- Name styles by aesthetic rather than by brand, so they can be reused without trademark worries.
- Recommend one active design system per project so the agent doesn't get conflicting instructions.
Related
DESIGN.md, getdesign.md, TypeUI DESIGN.md Extractor, VibePrompts, Refero Styles