design_styles

Generate five distinct UI design directions from a PRD.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fysoul17/one-query-v1 --skill design-styles-fysoul17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design_styles
Source: https://github.com/fysoul17/one-query-v1/tree/main/onequery/.claude/skills/devlyn%3Adesign-ui
Command: npx skills add https://github.com/fysoul17/one-query-v1 --skill design-styles-fysoul17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers need a fast, structured way to derive multiple visual directions from a PRD to align stakeholders and accelerate product decisions.

Core Features & Use Cases

  • Generates five distinct UI style directions from a single PRD.
  • Provides concrete visual statements and branding directions suitable for stakeholder reviews and design handoffs.
  • Supports escalation to a full design team for deeper exploration when needed.

Quick Start

Generate five portfolio-worthy UI style samples that visualize the PRD's goals and brand requirements.

Frequently Asked Questions about design_styles

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

FAQPage Schema
How do I generate UI design directions from a PRD?

To generate UI design directions from a PRD, you can use a structured style exploration process that analyzes your product requirements and delivers five distinct visual design options with concrete style statements and ready-to-implement design tokens.

What is the best way to explore multiple visual styles for stakeholder reviews?

The best way to explore visual styles for stakeholder reviews is to generate multiple distinct UI design directions from your PRD, providing concrete branding and interaction statements that accelerate product decisions and avoid generic outputs.

Can I get design tokens and specifications ready for implementation from a PRD?

Yes, you can derive phase-guided, self-contained specifications and design tokens ready for implementation directly from a PRD by applying a structured visual exploration process that maps branding and accessibility needs.

Does deriving UI styles automatically cover accessibility and interaction design?

Deriving UI styles through structured PRD analysis covers accessibility and interaction design by applying product requirements to generate visual exploration across branding, interaction, accessibility, and craft dimensions.

How do I avoid generic UI design outputs during style exploration?

You avoid generic UI design outputs during style exploration by generating five distinct, radical UI directions from your PRD that provide concrete visual statements and phase-guided specifications tailored to your specific product goals.

When do I need multiple UI style variations for product design?

You need multiple UI style variations when product teams require visual exploration across branding and interaction to align stakeholders, allowing for structured comparison of five distinct directions before escalating to a full design team.