design-system
/design-system
Audytuje, dokumentuje i rozbudowuje system designu: szuka niespójnych nazw i wpisanych na sztywno wartości oraz opisuje warianty i stany.
- Autor
- Suraj-Dhal ↗
- Repozytorium
- Suraj_Dhal_Portfolio ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 29.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 29.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Audytuje, dokumentuje i rozbudowuje system designu: szuka niespójnych nazw i wpisanych na sztywno wartości oraz opisuje warianty i stany.
Argumenty
/design-system [audit | document | extend] <component or system>
Oryginalny opis (EN)
Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.
Jak działa
- Usage
- Components of a Design System
- Principles
- Output — Audit
- Output — Document
- Output — Extend
- If Connectors Available
- Tips
Podgląd SKILL.md
--- name: design-system description: Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system. argument-hint: "[audit | document | extend] <component or system>" --- # /design-system 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 **design tool** is connected: - Audit components directly in Figma — check naming, variants, and token usage - Pull component properties and layer structure for documentation If **knowledge base** 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.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Suraj-Dhal/Suraj_Dhal_Portfolio | 100 | MIT |
| frontic/ui | 100 | MIT |
| akillness/jeo-skills | 100 | MIT |
| langwatch/langwatch | 100 | Apache-2.0 |
| borghei/Claude-Skills | 100 | MIT |
| alirezarezvani/claude-skills | 100 | MIT |
| sallaumen/elixir-agent-kit | 100 | MIT |
| davidelarocca/swift-harness | 100 | MIT |
| nextlevelbuilder/ui-ux-pro-max-skill | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3c8fe5b97374 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90figma-build
Buduje projekt w Figma z kodu lub opisu, wykorzystując istniejące komponenty, zmienne i style zamiast wartości wpisanych na sztywno. - 95wicked-garden-product-ui-reviewer
Przegląda spójność wizualną interfejsu: zgodność z systemem projektowym, wyszukiwanie wartości wpisanych na sztywno. - 100design-components
Opisuje katalog komponentów systemu projektowego: anatomia wspólna dla motywów, warianty, stany, kontrakt dostępności, sloty i18n oraz zakres zmian motywów, w design-system/COMPONENTS.md. - 100design-systems
Pomaga budować i utrzymywać bibliotekę komponentów i tokeny: architektura tokenów, projekt API komponentów, warianty, stany, dokumentacja i wdrażanie w kodzie. - 100design-system-implementation
Wdraża lub dopracowuje tokeny i komponenty interfejsu zgodne z kierunkiem produktu: API komponentów, warianty, stany i spójność między ekranami. - 90hue-recon
Audytuje użycie kolorów w kodzie projektu: wyszukuje niespójności, zakodowane na stałe wartości hex i niedostateczny kontrast.