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.
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
Build or evolve a design system by producing a Design System Operating Pack: charter, token model (incl. depth/elevation), component inventory + roadmap, blockframe-to-component mapping, documentation plan, and governance/adoption plan. Use for design systems, component libraries, design tokens, UI kits, and pattern libraries.
Skills-only equivalent of impeccable.style /normalize. Normalize design to match your design system and ensure consistency Use for frontend and UI design tasks.
Design System — Generate & Audit Visual Systems
Buttons, inputs, pills, badges, calendars, and other interactive components form a visual family — they share the same border-radius, colour logic, shadow scale, border style, and spacing rhythm. Inconsistency between them breaks the sense of a coherent product. Use when building or reviewing a component library, design system, or any set of UI components.
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.
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.
Review a web app or page for visual design quality — layout, typography, spacing, colour, hierarchy, consistency, interaction patterns, and responsive behaviour. Not a UX audit (that checks usability) — this checks whether it looks professional and polished. Produces a design findings report with screenshots. Triggers: 'design review', 'does this look good', 'review the design', 'check the layout', 'is this polished', 'visual review', 'design audit', 'make it look better', 'it looks off'.
Frontend and visual QA for responsive surfaces, screenshots, text fit, hierarchy, and interaction states.
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.