design
Design system reasoning. Maps product domain to style, palette, typography, and platform-specific patterns. Generates .rune/design-system.md as the shared design contract for all UI-generating skills.
Rune-kit · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Rune-kit/rune --skill designAbout this skill
name: design description: "Design system reasoning. Maps product domain to style, palette, typography, and platform-specific patterns. Generates .rune/design-system.md as the shared design contract for all UI-generating skills." metadata: author: runedev version: "0.9.0" layer: L2 model: opus group: creation tools: "Read, Write, Edit, Glob, Grep"
design
Purpose
Design system reasoning layer. Converts a product description into a concrete design system — style, color direction, typography pairing, platform conventions, and an explicit anti-pattern list for this domain. Writes .rune/design-system.md as the persistent design contract that all UI-generating skills read before producing code. Prevents AI-generated UI from defaulting to generic patterns ("purple accent, card grids, centered everything") that signal "not designed by a human."
Triggers
/rune design— manual invocation when starting a new UI project- Called by
cook(L1): frontend task detected, no.rune/design-system.mdexists - Called by
review(L2): AI anti-pattern detected — recommended to run design skill - Called by
perf(L2): Lighthouse Accessibility BLOCK — design foundation may be missing
Calls (outbound)
scout(L2): detect existing design tokens, component library, platform targetsasset-creator(L3): generate base visual assets (logo, OG image) from design systembrowser-pilot(L3): render the surface and inspect it before claiming any visual property holds (Step 5.4)review(L2): accessibility violations found → flag for fix in next code review
Called By (inbound)
cook(L1): before any frontend code generationscaffold(L1): design system for new projectbrainstorm(L2): when selected approach has UI/UX implicationsba(L2): when requirements include UI/UX componentsreview(L2): when AI anti-pattern detected in diffperf(L2): when Lighthouse Accessibility score blocks- User:
/rune designdirect invocation
Output Files
.rune/
└── design-system.md # Design contract for all UI-generating skills
Executable Steps
Step 0 — Load Design Reference
Load the design knowledge base before reasoning:
- Check for user-level override:
~/.claude/docs/design-dna.md- If exists →
Readit. This is the primary reference (user's curated taste).
- If exists →
- If no user override →
Readthe baseline:skills/design/DESIGN-REFERENCE.md(shipped with Rune) - The loaded reference provides: font pairings, chart selection, component architecture, color principles, UX checklist, interaction patterns, anti-pattern signatures
- Apply reference knowledge throughout Steps 3-5 (domain reasoning, token generation, checklist)
- When the domain involves any UI motion (transitions, animations, gestures, springs, micro-interactions) → also
Readskills/design/MOTION-CRAFT.md. It is the canonical motion authority: the should-it-animate frequency gate, easing/duration budgets (including peak-slope curve selection for large travel, and velocity continuity across keyframe joins), physicality (neverscale(0), origin-aware popovers), spring physics, gesture handoff, motion performance, the role→strategy reduced-motion framework, SVG-specific mechanics (user units,pathLength, SVGO), and a reverse-lookup vocabulary. Cite its exact values in the design-system motion section; never approximate curves or durations. When MOTION-CRAFT.md and DESIGN-REFERENCE.md disagree on a motion detail (easing, duration, interaction timing), MOTION-CRAFT.md wins — it is the deeper, motion-specific source; DESIGN-REFERENCE.md's Animation Timing / Interaction Patterns tables are the general baseline.
Advisory motion-audit mode: When asked to "improve the animations" / "make this feel better" / "what could be animated here", operate read-only — survey the motion surface against MOTION-CRAFT.md, report frequency-gated findings (and deliberately rejected candidates), and hand precise recipes to
cook/fix. Suggesting motion everywhere is worse than useless; expect to reject most candidates.
Why two layers: The baseline ships "good enough" universal design knowledge. Users who care about aesthetics create their own
design-dna.mdwith curated palettes, font pairings, and style preferences. The design skill works well with either — it just works better with a curated reference.
External Data Source
Design intelligence data from UI/UX Pro Max (MIT, 42.8k★).
Located at references/ui-pro-max-data/ — 161 palettes, 84 styles, 73 font pairings, 161 reasoning rules, 99 UX guidelines.
When references/ui-pro-max-data/ is available:
- Step 2: query
styles.csvfor domain-matched visual styles (expands from 10 → 84) - Step 3: query
ui-reasoning.csvfor industry-specific design rules (161 rules) - Step 3: query
colors.csvfor palette alternatives (expands from 10 → 161) - Step 6 (Anti-AI): cross-check proposed style against reasoning DB — if flagged as "AI-generic", suggest 3 alternatives
Step 1 — Discover
Invoke scout to detect:
- Platform target:
web|ios(SwiftUI) |android(Compose) |react-native|multi-platform - Existing design tokens: check for
tokens.json,design-system/,theme.ts,tailwind.config.*,variables.css - Component library in use: shadcn/ui | Radix | MUI | Ant Design | custom | none
- Framework: Next.js | Vite+React | SvelteKit | Vue | SwiftUI | Jetpack Compose | other
If .rune/design-system.md already exists: Read it, check Last Updated date. If < 30 days old, ask user whether to refresh or keep. Do NOT silently overwrite.
Step 2 — Classify Product Domain
From the user's task description + codebase context, classify product type:
| Category | Examples |
|---|---|
| Trading/Fintech | trading dashboard, portfolio tracker, payment app, crypto wallet |
| SaaS Dashboard |