A design department your coding agent can hire in one line
design.how ships skills, design systems and visuals that turn an agent into something with actual taste.

What it does
It’s a bundle of Agent Skills — the instruction files Claude Code, Cursor and Codex read — covering design work. The headline skill, design-system-boss, reads your app, picks a playbook, and orchestrates the others: build a system, migrate onto it, map values to tokens, document components, review screens. It commits to a run branch, never your default, and ends with one migrated flow plus a CI check before offering the full job with a size estimate.
The interesting bit
All the design skills share one glossary and one taste.md of defaults for bans, widths and voice — which you can replace with your own. It’s opinionated design judgment as a config file, which is either brilliant or the most audacious part of the whole thing.
Key highlights
- Four shadcn-based design systems, each with its own skill: Glaze (glassy, AI products), Lime (warm, consumer), Quartz (cold, dev tools), Sodium (sharp and mono, infrastructure)
- Beyond UI:
make-fontgenerates a custom typeface (needs Python withfonttoolsand friends),make-motionproduces motion graphics videos - A “Vault” of visuals — kinetic typography, shaders, WebGL pieces — each installable as its own skill
- Ships with its own evals:
node evals/run.mjs --lintlints the skills themselves - MIT licensed, works with any agent that reads Agent Skills
Caveats
- Screenshot-taking skills require Playwright plus a Chromium/Chrome install;
make-fontdrags in a Python toolchain — the dependency surface is wider than “just add a skill” suggests - The skills lean on shared reference files, so installing a single skill alone means also pulling
build-design-systemfor its glossary and taste defaults
Verdict Worth a look if your agent-built UI has that unmistakable LLM-gray sameness and you want a structured fix rather than another prompt. If you already have a real design system and humans who maintain it, this is less for you.
Frequently asked
- What is arla6ka/design.how?
- design.how ships skills, design systems and visuals that turn an agent into something with actual taste.
- Is design.how open source?
- Yes — arla6ka/design.how is open source, released under the MIT license.
- What language is design.how written in?
- arla6ka/design.how is primarily written in TypeScript.
- How popular is design.how?
- arla6ka/design.how has 616 stars on GitHub.
- Where can I find design.how?
- arla6ka/design.how is on GitHub at https://github.com/arla6ka/design.how.