designer-skills vs Kami
239 design skills, 88 commands and 33 plugins for Claude Code and Gemini CLI — research, design systems, UI, interaction and delivery, written for agents to actually execute. — versus — A document design system for AI agents: one constraint language and eight templates (plus a landing-page system) so agent-produced documents ship consistent instead of generic gray.
Two routes to design-literate agents: designer-skills is a broad pack of design-craft skills; Kami is one strict constraint system focused on making every shipped document consistent.
| designer-skills | Kami | |
|---|---|---|
| Stars | 1.8k | 9.8k |
| Forks | 307 | 458 |
| Language | Markdown | HTML |
| License | MIT | MIT |
| Last activity | 1 months ago | 4 days ago |
| Topics | skills | skills |
| Curated connections | 4 | 1 |
designer-skills — the curator's take
The largest coherent skill pack for design work: five collections covering research→systems→UI→interaction→delivery, installable straight from Claude Code's plugin marketplace with genuinely non-technical instructions. If you're a designer adopting agents (or an engineer faking design taste), this is the fastest on-ramp. NOT a design tool itself — it's prompts-as-skills, so output quality tracks the underlying model, and 239 skills means uneven depth: audit the ones you'll actually use rather than installing all five collections on day one.
Kami — the curator's take
Built on a sharp diagnosis: AI can produce documents, but without a design system every session drifts into inconsistent, generic output. Kami is the constraint language — strict enough that agents produce shippable pages, simple enough that they follow it reliably. Part of tw93's agent trilogy (Kaku writes code, Waza drills habits, Kami delivers documents). NOT a generator itself — it's the discipline your agent works within; you still bring the agent and the content.