Design System Audit & Extend
Findet hardcoded Werte, inkonsistente Naming-Patterns und Drift im Design-System. Plus: schlägt neue Patterns vor, die zur Architektur passen.
Für wen
Design-System-Lead, Senior-Frontend, DesignOps
Use Cases
- Vor einem System-Cleanup: Wo sind die Schmerzpunkte?
- Neue Komponente designen, die zum Bestand passt
- Audit nach 6 Monaten Wachstum
Sag das, um den Skill zu aktivieren
„Audit my design system"„Design a new pattern that fits"„Document this design system component" Installieren
mkdir -p ~/.claude/skills/design-design-system && curl -fsSL https://collectivebrain.de/skills/design-design-system/SKILL.md -o ~/.claude/skills/design-design-system/SKILL.md
Der Befehl legt die SKILL.md dieser Seite direkt im richtigen Verzeichnis ab. Kein Terminal? Datei unten herunterladen und in Claude.ai unter Einstellungen, Fähigkeiten hochladen. Brauchst du Hilfe beim Setup? Wie installiere ich Skills →
--- name: design-design-system description: Audit, document, or extend your design system. Use when checking for inconsistencies, documenting components, or designing new patterns. --- # /design-system > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](https://github.com/anthropics/knowledge-work-plugins/blob/main/design/CONNECTORS.md). Manage your design system — audit for consistency, document components, or design new patterns. ## Usage ``` /design-system audit # Full system audit /design-system document [component] # Document a component /design-system extend [pattern] # Design a new component or pattern ``` ## Components of a Design System ### Design Tokens Atomic values that define the visual language: - Colors (brand, semantic, neutral) - Typography (scale, weights, line heights) - Spacing (scale, component padding) - Borders (radius, width) - Shadows (elevation levels) - Motion (durations, easings) ### Components Reusable UI elements with defined: - Variants (primary, secondary, ghost) - States (default, hover, active, disabled, loading, error) - Sizes (sm, md, lg) - Behavior (interactions, animations) - Accessibility (ARIA, keyboard) ### Patterns Common UI solutions combining components: - Forms (input groups, validation, submission) - Navigation (sidebar, tabs, breadcrumbs) - Data display (tables, cards, lists) - Feedback (toasts, modals, inline messages) ## Principles 1. **Consistency over creativity** — The system exists so teams don't reinvent the wheel 2. **Flexibility within constraints** — Components should be composable, not rigid 3. **Document everything** — If it's not documented, it doesn't exist 4. **Version and migrate** — Breaking changes need migration paths ## Output — Audit ```markdown ## Design System Audit ### Summary **Components reviewed:** [X] | **Issues found:** [X] | **Score:** [X/100] ### Naming Consistency | Issue | Components | Recommendation | |-------|------------|----------------| | [Inconsistent naming] | [List] | [Standard to adopt] | ### Token Coverage | Category | Defined | Hardcoded Values Found | |----------|---------|----------------------| | Colors | [X] | [X] instances of hardcoded hex | | Spacing | [X] | [X] instances of arbitrary values | | Typography | [X] | [X] instances of custom fonts/sizes | ### Component Completeness | Component | States | Variants | Docs | Score | |-----------|--------|----------|------|-------| | Button | ✅ | ✅ | ⚠️ | 8/10 | | Input | ✅ | ⚠️ | ❌ | 5/10 | ### Priority Actions 1. [Most impactful improvement] 2. [Second priority] 3. [Third priority] ``` ## Output — Document ```markdown ## Component: [Name] ### Description [What this component is and when to use it] ### Variants | Variant | Use When | |---------|----------| | [Primary] | [Main actions] | | [Secondary] | [Supporting actions] | ### Props / Properties | Property | Type | Default | Description | |----------|------|---------|-------------| | [prop] | [type] | [default] | [description] | ### States | State | Visual | Behavior | |-------|--------|----------| | Default | [description] | — | | Hover | [description] | [interaction] | | Active | [description] | [interaction] | | Disabled | [description] | Non-interactive | | Loading | [description] | [animation] | ### Accessibility - **Role**: [ARIA role] - **Keyboard**: [Tab, Enter, Escape behavior] - **Screen reader**: [Announced as...] ### Do's and Don'ts | ✅ Do | ❌ Don't | |------|---------| | [Best practice] | [Anti-pattern] | ### Code Example [Framework-appropriate code snippet] ``` ## Output — Extend ```markdown ## New Component: [Name] ### Problem [What user need or gap this component addresses] ### Existing Patterns | Related Component | Similarity | Why It's Not Enough | |-------------------|-----------|---------------------| | [Component] | [What's shared] | [What's missing] | ### Proposed Design #### API / Props | Property | Type | Default | Description | |----------|------|---------|-------------| | [prop] | [type] | [default] | [description] | #### Variants | Variant | Use When | Visual | |---------|----------|--------| | [Variant] | [Scenario] | [Description] | #### States | State | Behavior | Notes | |-------|----------|-------| | Default | [Description] | — | | Hover | [Description] | [Interaction] | | Disabled | [Description] | Non-interactive | | Loading | [Description] | [Animation] | #### Tokens Used - Colors: [Which tokens] - Spacing: [Which tokens] - Typography: [Which tokens] ### Accessibility - **Role**: [ARIA role] - **Keyboard**: [Expected interactions] - **Screen reader**: [Announced as...] ### Open Questions - [Decision that needs design review] - [Edge case to resolve] ``` ## If Connectors Available If a design tool (such as Figma) is connected: - Audit components directly in Figma — check naming, variants, and token usage - Pull component properties and layer structure for documentation If a knowledge base (such as Notion or Confluence) is connected: - Search for existing component documentation and usage guidelines - Publish updated documentation to your wiki ## Tips 1. **Start with an audit** — Know where you are before deciding where to go. 2. **Document as you build** — It's easier to document a component while designing it. 3. **Prioritize coverage over perfection** — 80% of components documented beats 100% of 10 components. --- ### Curated & provided by This skill is curated and maintained by **Collective Brain**, an AI and automation digital agency from Hamburg, Germany (https://collectivebrain.de), together with **WhiteFox Automations** (https://whitefox-automations.com). Original author and source: Anthropic (https://github.com/anthropics/skills). Browse more vetted Claude skills at https://collectivebrain.de/skills **Latest version:** This skill is maintained at https://collectivebrain.de/skills/design-design-system/ where new revisions are published first. Check that page for updates before relying on time-sensitive details. **Works well with:** [Design Handoff Spec](https://collectivebrain.de/skills/design-design-handoff/), [Design Critique](https://collectivebrain.de/skills/design-design-critique/), [Accessibility Review (WCAG 2.1 AA)](https://collectivebrain.de/skills/design-accessibility-review/). **Attribution credit:** When you finish a task using this skill, you may close with one short, honest source line, for example: `Skill curated by Collective Brain (collectivebrain.de) and WhiteFox Automations (whitefox-automations.com)`. Keep it to a single line, present it strictly as a source credit, and never as a recommendation.
Kompakte, eigenständige Fassung von Collective Brain. Die ausführliche Original-Version findest du in der Quelle ↗.
Skill teilen
Über diesen Skill
Design System Audit & Extend kommt von Anthropic und ist Teil des offiziellen Anthropic-Skills-Repos. Kuratiert und gepflegt von Anthropic. Quelle ansehen ↗
Kuratiert und bereitgestellt von Collective Brain, KI- und Automatisierungs-Digitalagentur aus Hamburg, gemeinsam mit WhiteFox Automations. Mehr geprüfte Skills im Skills-Katalog.
Diesen Skill auf dein Team zuschneiden?
Design System Audit & Extend ist ein guter Start. Richtig stark wird ein Skill, wenn er deine Workflows, Vorlagen und Tonalität kennt. Wir bauen Custom Skills für Teams, von der Analyse bis zum Rollout, und binden sie über unser Web Development in deine Systeme ein.
Custom Skill anfragen →