designer

Generate accessible user interfaces using design system tokens and WCAG AA standards.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/roborew/opencode --skill designer-roborew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: designer
Source: https://github.com/roborew/opencode/tree/main/skills/designer
Command: npx skills add https://github.com/roborew/opencode --skill designer-roborew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of creating user interfaces that are not only visually appealing but also highly accessible, consistent with project design systems, and production-ready.

Core Features & Use Cases

  • UI Generation: Creates elegant, accessible, production-ready user interfaces.
  • Design System Adherence: Discovers and strictly follows existing project design tokens, component primitives, and styling patterns.
  • Accessibility Compliance: Enforces WCAG AA contrast ratios, visible focus states, semantic HTML, and keyboard operability.
  • Use Case: A developer needs to implement a new user profile form. The designer skill will ensure the form uses the project's existing input components, adheres to spacing and color tokens, and meets all accessibility requirements before any code is finalized.

Quick Start

Use the designer skill to create a new button component following the project's design system.

Frequently Asked Questions about designer

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

FAQPage Schema
How do I generate accessible user interfaces that comply with WCAG AA standards?

Generate accessible user interfaces by enforcing WCAG AA contrast ratios, visible focus states, semantic HTML, and keyboard operability. This approach ensures your UI components meet strict accessibility compliance and are production-ready without manual auditing.

How do I ensure my new UI components match an existing design system?

Ensure UI components match a design system by discovering and strictly following project design tokens, component primitives, and styling patterns. This prevents visual conflicts and maintains consistency across the frontend application architecture.

What is the best way to build a production-ready frontend form without breaking design consistency?

Build production-ready frontend forms by scoping execution to specific design stages and prioritizing existing design tokens and component primitives. This guarantees accessibility and visual consistency before any code is finalized.

Does this UI generation approach support keyboard operability and semantic HTML?

Yes, this UI generation approach supports keyboard operability and semantic HTML by strictly enforcing accessibility rules. It ensures all generated components are fully navigable via keyboard and structurally semantic for screen reader compatibility.

Can I use this to scope UI design tasks within a larger development plan?

Yes, you can scope UI design tasks within a larger development plan by executing specific stages owned by the designer role within a StagePlan artifact. This isolates UI generation and accessibility enforcement to precise workflow phases.

When do I need to discover design tokens before generating UI components?

Discover design tokens before generating UI components when working within an established project to ensure consistency and prevent conflicts. Prioritizing these tokens guarantees that new interfaces adhere to existing visual and styling patterns.