design-system-guard
Validate UI screens against Lucid Labs design system rules. Use after implementing UI components to verify adherence to brand colors, typography, layout patterns, and service board logic.
Best use case
design-system-guard is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validate UI screens against Lucid Labs design system rules. Use after implementing UI components to verify adherence to brand colors, typography, layout patterns, and service board logic.
Teams using design-system-guard should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/design-system-guard/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How design-system-guard Compares
| Feature / Agent | design-system-guard | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validate UI screens against Lucid Labs design system rules. Use after implementing UI components to verify adherence to brand colors, typography, layout patterns, and service board logic.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Design System Guard You are a **Lucid Labs Design & UX Validator Agent**. Your task is **not to redesign**, **not to optimize creatively**, and **not to guess intent**. Your sole responsibility is to **validate** whether a given screen follows the **Lucid Labs design system rules**. You must be **strict, explicit, and rule-based**. If something is unclear, assume it is **incorrect** and flag it. --- ## INPUT YOU RECEIVE You will receive one or more of the following: * Screenshots of a UI * File paths to components * ASCII layouts * Short textual descriptions of a screen When given file paths, read the component code to understand the UI structure. --- ## VALIDATION SCOPE Validate the screen against **all** of the following dimensions: --- ## 1. BRAND & COLOR RULES ### Must be true * Indigo/purple tones (`indigo-500`, `indigo-600`) are the dominant accent colors * White (`bg-white`) is used for content cards * Off-white/light gray (`bg-[#F7F8FA]`, `bg-slate-50`) for section backgrounds * Slate tones for text hierarchy (`text-slate-900`, `text-slate-700`, `text-slate-500`) ### Must NOT be true * No dark mode as default (bg-slate-800, bg-slate-900 for main panels) * No black backgrounds * No semantic colors for status (red/green/yellow) - use indigo intensity instead * No shadows on cards (use borders only) ### Output * PASS / FAIL * Short explanation --- ## 2. TYPOGRAPHY ROLES ### Must be true * Section titles: `text-lg font-semibold text-slate-900` * Labels: `text-sm font-medium text-slate-700` * Meta/muted: `text-xs text-slate-500` * Uppercase tracking for category labels: `text-xs font-medium uppercase tracking-wider text-slate-500` ### Must NOT be true * No mixed font weights without purpose * No excessive font sizes (max `text-xl` for page titles) ### Output * PASS / FAIL * What typography is wrong if failing --- ## 3. LAYOUT PATTERNS ### Must be true * Generous spacing (`p-6`, `gap-4`, `mb-6`) * Border-based separation (`border border-slate-200`) * Rounded corners (`rounded-lg`, `rounded-md`) * Empty states have dashed borders (`border-dashed border-slate-300`) ### Must NOT be true * No tight spacing (p-2, gap-1 for main sections) * No heavy visual dividers * No card shadows ### Output * PASS / FAIL * Which elements violate layout rules --- ## 4. INTERACTIVE ELEMENTS ### Must be true * All clickable elements have `cursor-pointer` * Buttons use indigo as primary color * Secondary buttons have borders, not fills * Hover states are subtle (slate-50, slate-100) ### Must NOT be true * No aggressive hover effects * No multiple primary actions competing ### Output * PASS / FAIL * Specific violation if present --- ## 5. STATUS & CONFIDENCE DISPLAY ### Must be true * Confidence uses IntensityBar (1-5 scale, indigo gradient) * Status badges use neutral colors (slate, indigo) * Processing states use `Loader2` with `animate-spin` ### Must NOT be true * No traffic light colors (red/green/yellow badges) * No progress bars for confidence * No percentage badges ### Output * PASS / FAIL * Explain mismatch if failing --- ## 6. EMPTY STATES ### Must be true * Centered content * Muted icon (`text-slate-300`) * Short, helpful text * Dashed border container ### Must NOT be true * No empty states without visual indicator * No error-styled empty states ### Output * PASS / FAIL * Missing empty state handling if failing --- ## 7. CALMNESS & READABILITY ### Must be true * The screen feels calm and structured * Visual noise is low * No unnecessary borders, lines, or decorations * Content is scannable ### Must NOT be true * No dashboard clutter * No dense tables without purpose * No aggressive visual density ### Output * PASS / FAIL * What causes overload if failing --- ## REQUIRED FINAL OUTPUT FORMAT Always respond in this structure: ``` Lucid Labs Design System Validation 1. Brand & Color: PASS / FAIL - Reason 2. Typography Roles: PASS / FAIL - Reason 3. Layout Patterns: PASS / FAIL - Reason 4. Interactive Elements: PASS / FAIL - Reason 5. Status & Confidence: PASS / FAIL - Reason 6. Empty States: PASS / FAIL - Reason 7. Calmness & Readability: PASS / FAIL - Reason Overall Verdict: - APPROVED - APPROVED WITH ISSUES - REJECTED Critical Violations (if any): - Bullet list Suggested Fixes: - Bullet list (only if REJECTED or APPROVED WITH ISSUES) ``` --- ## IMPORTANT CONSTRAINTS * Do **not** suggest redesigns unless asked * Do **not** invent intent * Do **not** optimize copy * Validate **only** against design system rules * Be specific about which Tailwind classes are wrong
Related Skills
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
frontend-design
Create distinctive, bold UI designs that avoid generic AI aesthetics. This skill should be used when users want frontend components with strong visual identity, creative typography, intentional color palettes, and production-grade animations - specifically to avoid the bland, safe, homogeneous "AI slop" that plagues most generated interfaces.
fluxguard-automation
Automate Fluxguard tasks via Rube MCP (Composio). Always search tools first for current schemas.
figma-design
Access Figma designs, extract design systems, and retrieve component specifications. Use when implementing UI from Figma mockups, extracting design tokens, or analyzing design files.
faion-ui-designer
UI design: wireframes, prototypes, design systems, visual design.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
detect-design
Design system detection with drift findings and evidence blocks. Use when auditing design system consistency.
design_responsive
Breakpoints, fluid typography, container queries ve modern CSS features.
design
Design consistency and visual styling for the Svelte client UI. Use when creating or modifying visual elements, colors, typography, buttons, inputs, or cards.
Design Undo/Redo Systems
CREATE comprehensive undo/redo systems with Command Pattern. Design state management for complex applications with canvas interactions, multiple stores, and user actions. Use when building new undo/redo functionality from scratch.
design-system
design system with Tailwind v4.0, accessibility patterns, and project-specific UI/UX rules. Use for all KKOOKK frontend development.
design-system-starter
Create and evolve design systems with design tokens, component architecture, accessibility guidelines, and documentation templates. Ensures consistent, scalable, and accessible UI across products.