ux-brief

Design system templates and patterns for UI/UX briefs. Used by /majestic:ux-brief command.

⭐13stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026⬇️5downloads

When & Why to Use This Skill

The ux-brief skill streamlines the UI/UX design-to-development workflow by generating comprehensive design system templates and patterns. It focuses on creating 'junior-dev ready' documentation that includes precise specifications for colors, typography, spacing, and component states, ensuring that design briefs are immediately actionable and eliminate the need for follow-up clarifications.

Use Cases

  • Standardizing Design Handoffs: Generate exhaustive UI/UX briefs using the /majestic:ux-brief command to provide developers with all necessary CSS values, tokens, and configuration examples.
  • Design System Bootstrapping: Quickly establish a foundational design system structure with predefined patterns for typography scales, color palettes, and layout spacing logic.
  • Component Behavior Specification: Define clear visual states and functional behaviors for UI components to ensure consistency across different frameworks and implementation stages.
  • Accelerating Frontend Development: Produce 'copy-paste ready' classes and configurations that allow developers to move directly from a brief to functional code without interpreting vague design requirements.
nameux-brief
descriptionDesign system templates and patterns for UI/UX briefs. Used by /majestic:ux-brief command.

UX Brief Skill

Provides design system templates and patterns for creating comprehensive UI/UX briefs.

When to Use

This skill is automatically invoked by the /majestic:ux-brief command. It provides:

  • Design system template structure
  • Color, typography, and spacing specifications
  • Component state definitions
  • Framework configuration examples

Template

Read the design system template: resources/design-system-template.md

Key Principles

  • Junior-dev ready: Document should be so complete that no follow-up questions are needed
  • Copy-paste ready: All classes, values, and configs should be directly usable
  • Commit to a direction: Avoid wishy-washy "a bit of everything" designs
  • Avoid AI slop: No Inter font, no purple gradients, no predictable layouts