skills/jesusexpositol/ixlab/ixlab-design-system

ixlab-design-system

SKILL.md

IxLab Design System

Use this skill to create or evolve design/system.md.

The design system is a project artifact, not a mood board. It should be specific enough to guide consistent design and implementation decisions across entities.

Read These Files

  • config/ixlab.config.md
  • templates/design-system.md
  • existing design/system.md when present
  • relevant existing entity artifacts when they reveal stable patterns worth systematizing
  • references/visual-principles.md when present
  • references/anti-patterns.md when present
  • references/motion-guidelines.md when present
  • references/accessibility.md when present

Responsibilities

  • define the shared visual and interaction foundation
  • encode stable decisions that should persist between sessions
  • give the UI Designer and Design Engineer a concrete baseline

Workflow

  1. Read the project configuration.
  2. If design/system.md exists, update it instead of replacing it blindly.
  3. Load the relevant reference files selectively instead of reading the whole references/ directory.
  4. Use templates/design-system.md as the output structure.
  5. Define:
    • system intent
    • product-facing design principles
    • color usage rules
    • typography and rhythm
    • spacing, radius, and depth
    • motion defaults
    • component conventions
    • accessibility baseline
  6. Translate design_variance, motion_intensity, and visual_density from config into concrete system decisions instead of leaving them abstract.
  7. Keep the system opinionated, but tied to product context.

Quality Rules

  • Avoid vague adjectives without operational meaning.
  • Prefer concrete rules over aesthetic slogans.
  • Do not copy a generic startup design language.
  • Keep the system implementable by a frontend engineer.
  • Make tradeoffs explicit when the product context demands them.
  • Do not omit template sections. Use N/A only when a section is truly not applicable.
  • Write anti-patterns and defaults as enforceable decisions, not inspiration.

Finish Condition

design/system.md should be usable as a stable reference for both the UI Designer and the Design Engineer.

Weekly Installs
2
First Seen
8 days ago
Installed on
codex2
cursor1
claude-code1