dvy1987/agent-loom / .agents/skills/design-system
design-system
VerifiedTurn a chosen design direction into a canonical DESIGN.md plus production tokens that don't look vibecoded — state-level colors (8-step neutral ramp, rest/hover/active/ disabled, focus ring), APCA-checked contrast, typography, spacing/radius/motion/elevation, an icon strategy, and component contracts for the core atoms. Emits tokens in the project's stack format (shadcn HSL vars or Tailwind v4 @theme). Load when the user asks to build a design system, generate design tokens, create a DESIGN.md, set up a theme, design a color or type system, pick icons, or when frontend-design routes here. Replaces design-tokens-craft and icon-craft. Sub-skill of frontend-design. Reads DIRECTION.md first.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.5 KB |
| references/banned-palettes.md | markdown | 2.8 KB |
| references/design-md-template.md | markdown | 3.8 KB |
| references/examples.md | markdown | 1.8 KB |
| references/icon-strategies.md | markdown | 4.3 KB |
| references/state-tokens.md | markdown | 4.2 KB |
| references/svg-craft.md | markdown | 3.6 KB |
| references/token-recipes.md | markdown | 7.4 KB |
| references/typography-pairings.md | markdown | 5.2 KB |
references/banned-palettes.md
View on GitHub# Banned Palettes (vibecoded tells)
If any of these appear in generated tokens without an explicit, archetype-grounded justification, REJECT and regenerate.
## Color tells
- `slate-50` through `slate-950` as the primary grayscale (Tailwind default — instantly recognized)
- `zinc-*` or `gray-*` as primary grayscale (same problem)
- `blue-600` (#2563EB) as the only accent (over-used "AI default")
- `from-purple-500 to-pink-500` gradient or `from-indigo-500 to-violet-500` gradient
- 9-step grayscale dump (50, 100, 200, 300, 400, 500, 600, 700, 800, 900) — most products need 5–7 grays
- Pure black `#000000` background — only acceptable in `brutalist-distinctive`
- Pure white `#FFFFFF` background — only acceptable in `enterprise-trust` and `brutalist-distinctive`
- Identical hex values for "primary" and "brand" tokens (means the system is one-color, not a system)
- Auto-generated dark mode by inverting lightness (must be hand-set per archetype)
## Typography tells
- Inter as the only font on the page (across display + body + mono)
- "Inter Display" + "Inter" as a "pairing" (it's one family — not a real pair)
- Tailwind's `font-sans` left as default in tokens (means no decision was made)
- `tracking-tight` applied uniformly to all headings
- Body line-height 1 (cramped) or > 1.8 (drifty) without editorial justification
- Default font sizes from Tailwind's scale untouched (1rem, 1.125rem, 1.25rem...) when archetype demands a custom scale
## Spacing tells
- Linear spacing scale (4, 8, 12, 16, 20, 24, 28...) — use log-spaced
- 100+ spacing tokens (over-engineered)
- 0 distinct spacing tokens (under-engineered)
- Border-radius scale starting at 4 and ending at `9999px` with no archetype rationale
## Motion tells
- Single `transition-all duration-300` token used everywhere
- `ease-in-out` literal — pick a real cubic-bezier
- 5+ duration tokens (most archetypes need 3–4)
- No `prefers-reduced-motion` token override
## Elevation tells
- 6+ shadow elevations (most archetypes need 0–3)
- Default Tailwind shadows (`shadow-sm`, `shadow-md`, `shadow-lg`) untouched — they're calibrated for one specific aesthetic
- Drop shadows on every card
---
## Audit script (mental checklist)
After generating tokens, scan the output:
1. Any literal `slate-*` / `zinc-*` / `gray-*` hex values? → reject
2. Any `from-purple-* to-pink-*` gradient definition? → reject
3. Is the typography token output using one family for everything? → reject (unless archetype is brutalist-mono)
4. Is the dark mode mathematically inverted? → reject, hand-set
5. Are there 9 grays defined? → trim to 5–7
6. Is there a single duration of 300ms used everywhere? → split per archetype motion budget
If any reject hits, return to Step 4 of the workflow and regenerate the offending section grounded in the archetype recipe.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |