Loading...
Loading...
Found 19 Skills
Normalize design to match your design system and ensure consistency
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library.
After building any UI component, extract the visual patterns that matter for consistency and save them to ui-registry.md. So every component built after this one matches what came before.
Creates comprehensive design systems with typography, colors, components, and documentation for consistent UI development. Use when establishing design standards, building component libraries, or ensuring cross-team consistency. Keywords: design-tokens, typography, spacing, color-palette, components, patterns, variables, dark-mode, theming, CSS-variables, accessibility, WCAG, responsive, grid-system, breakpoints, design-scale, semantic-tokens, component-library, style-guide, documentation, Figma, Storybook, brand-consistency, design-principles
Create and manage project-specific design systems for SaaS applications. Use when starting a new app (CREATE mode), updating an existing design system (MODIFY mode), or building features that need to follow established patterns (WORK WITHIN mode). Outputs to instructions/design-system.md as the single source of truth for all UX/UI decisions.
Skills-only equivalent of impeccable.style /normalize. Normalize design to match your design system and ensure consistency Use for frontend and UI design tasks.
Frontend and visual QA for responsive surfaces, screenshots, text fit, hierarchy, and interaction states.
Audits and realigns UI to match design system standards, spacing, tokens, and patterns. Use when the user mentions consistency, design drift, mismatched styles, tokens, or wants to bring a feature back in line with the system.
Design engineering skill for Claude Code that enforces consistent UI patterns through memory, craft principles, and systematic design tokens.
Design System — Generate & Audit Visual Systems
Automatically injects the project's extracted design soul into any frontend task. Use this skill on EVERY request that involves building, editing, or reviewing UI — including components, pages, layouts, styles, animations, and design decisions. Triggers on: any prompt containing words like "build", "create", "make", "design", "component", "page", "layout", "button", "form", "card", "nav", "header", "modal", "style", "css", "tailwind", "animate", "responsive", "ui", "frontend", "screen", "dashboard", "landing", "section", or any request to write JSX, TSX, HTML, or CSS. Do NOT trigger on backend-only tasks, database queries, API routes with no UI, or pure logic/utility functions with no visual output. This skill has no slash command — it runs silently in the background on every frontend task. The user never needs to invoke it manually.
Scans the current project's frontend files, finds the components most out of alignment with .marrow.md, and fixes them automatically — without the user specifying a target. The zero-argument soul alignment sweep. Use this skill when the user wants to broadly align the project to the design soul, fix whatever is most off without specifying a file, or run a soul sweep across multiple components at once. Triggers on: /marrow-magic, or prompts like "fix everything to match marrow", "align my whole project", "soul sweep", "fix the worst violations", "everything feels off", "clean up all components to match the design". Requires .marrow.md to exist. If not found, instructs user to run /marrow first.