SlipItIn/.agents/skills/ultimate-design-system-master/SKILL.md

name, description, metadata

name	description	metadata
ultimate-design-system-master	Create comprehensive design systems, brand identities, and UI component libraries. Use when the user says "create design system", "build brand identity", "design UI components", "generate design tokens", "create figma specs", "review my design", "analyze design trends", "audit accessibility", "convert design to code", or "create presentation deck". Covers 10 specialized roles from system architecture to executive presentations.	author version date license category ft.ia.br 2.2 2026-03-08 Apache 2.0 code-scaffolding-and-templates

Ultimate Design System Master

Workflow

1. Gather briefing — Apply the 18-question questionnaire in references/briefing-questionnaire.md. Retain all answers in conversation context.
2. Present menu — Display the 10 generators below. Accept single or multiple selections.
3. Execute — Load the selected references/prompt-*.md file as the sole source. Apply briefing data. Generate output.
4. Loop — After each delivery, present the menu again until the user selects "Exit".

Menu

#	Generator	Role-play	Reference
1	Design System Architect	Apple Principal Designer → HIG-level system	prompt-01
2	Brand Identity Creator	Pentagram Creative Director → strategy + rationale	prompt-02
3	UI/UX Pattern Master	Apple Senior UI Designer → 8 detailed screens	prompt-03
4	Marketing Asset Factory	Top agency Creative Director → 47+ assets	prompt-04
5	Figma Auto-Layout Expert	Figma Design Ops Specialist → technical specs	prompt-05
6	Design Critique Partner	Apple Design Director → Nielsen critique + alternatives	prompt-06
7	Design Trend Synthesizer	frog Design Researcher → 2026 trends + roadmap	prompt-07
8	Accessibility Auditor	Apple Accessibility Specialist → WCAG 2.2 AA audit	prompt-08
9	Design-to-Code Translator	Vercel Design Engineer → production-ready code	prompt-09
10	Presentation Designer	Apple Presentation Designer → executive narrative	prompt-10
11	Exit

Rules

• Maintain full consistency with briefing data across all outputs.
• Load only the selected prompt file — do not mix prompts.
• Use clear, professional, immediately usable formatting.
• Present the menu again after each delivery.

Quality Checklist

• All 18 briefing questions answered before generating output.
• Only the selected prompt file was loaded.
• Output is consistent with the briefing (brand name, colors, tone, platform, tech stack).
• Formatting is production-ready (no placeholders left unfilled).
• Menu presented again after delivery.