ui-design

Define UI design specifications from product requirements with design tokens and responsive rules.

133|9|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill ui-design-lync-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-design
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/ui-design
Command: npx skills add https://github.com/lync-cyber/CataForge --skill ui-design-lync-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn product requirements into a coherent UI design direction, so teams can make consistent decisions on layout, components, tokens, and responsive behavior without drifting into fragmented styles.

Core Features & Use Cases

  • Design Direction Definition: Establishes the visual strategy, tone, and reference cues before any tokens are created.
  • Design System Token Planning: Defines color, typography, spacing, and radius choices with explicit design intent and consistency checks.
  • Component and Page Specification: Produces reusable component definitions, page layouts, navigation structure, and responsive rules for implementation.
  • Use Case: Use this Skill when you have a PRD or feature requirement and need a structured UI specification that can guide designers and developers toward the same result.

Quick Start

Ask the AI to turn your PRD or feature requirement into a complete UI specification with design direction, tokens, components, pages, and responsive strategy.

Frequently Asked Questions about ui-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD into a complete UI design specification?

To turn a PRD into a UI design specification, you establish the visual direction, define design tokens, set component rules, plan page layouts, and determine responsive behavior for consistent implementation across screens.

What is the best way to maintain design system consistency across multiple screens?

Maintaining design system consistency requires defining explicit design tokens for color, typography, spacing, and radius, alongside structured reusable component rules and navigation specifications for all page layouts.

How do I plan responsive design breakpoints from feature requirements?

Planning responsive design breakpoints from feature requirements involves establishing a breakpoint strategy alongside page layout states, ensuring the UI adapts correctly while preserving design intent across different devices.

Can I generate design tokens directly from product requirements?

Yes, you can generate design tokens from product requirements by first defining the visual strategy and tone, then establishing explicit color, typography, spacing, and radius choices with consistency checks.

Does this approach work for component catalog maintenance?

Yes, this approach works for component catalog maintenance by producing reusable component definitions and page specifications, ensuring design system consistency and governance across new feature implementations.

What limitations exist when defining page layouts from a PRD?

Defining page layouts from a PRD requires structured output for design intent, token governance, and navigation states; without clear product requirements, the resulting UI specification may lack coherent visual direction.