design-grill

Interview stakeholders to generate a project-root DESIGN-BRIEF.md for UI design.

3|Updated May 16, 2026
One-click install
npx skills add https://github.com/dawitlabs/ui-skills --skill design-grill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-grill
Source: https://github.com/dawitlabs/ui-skills/tree/main/skills/design-grill
Command: npx skills add https://github.com/dawitlabs/ui-skills --skill design-grill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Prevents UI work from starting without a shared, specific visual direction by running a guided, contradiction-aware interview that produces a reusable DESIGN-BRIEF.md north star for the project.

Core Features & Use Cases

  • One-question-at-a-time design interview: Extracts product category, target persona, brand personality, emotional goals, visual references, color direction, typography, component style, animation level, and dark mode requirements.
  • Reads existing context first: Checks for an existing DESIGN-BRIEF.md, partially implemented tokens, CSS/config artifacts, and prior skill screenshots to avoid re-asking decisions already made.
  • Surfaces contradictions before committing: Detects incompatible answers (e.g., dense vs whitespace-heavy, minimal motion vs highly expressive landing) and resolves them prior to writing the brief.
  • Generates a project-root artifact: Writes DESIGN-BRIEF.md including “Decisions Made,” “Ruled Out,” and “Open Questions” so downstream skills (UI/UX, tokens, animation, landing) can act consistently.

Quick Start

Run design-grill for a new project by asking it, one question at a time, to determine product category, audience, brand personality, and the full visual direction so it can generate a DESIGN-BRIEF.md you can use for the next skills.

Frequently Asked Questions about design-grill

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

FAQPage Schema
How do I create a design brief for a new product UI?

To create a design brief for a new product UI, you can run a guided interview that extracts product category, target persona, brand personality, and visual references to generate a project-root DESIGN-BRIEF.md artifact.

What is the best way to resolve contradictions in UI design direction?

Resolving contradictions in UI design direction involves detecting incompatible answers like dense versus whitespace-heavy layouts and resolving them before writing the final design brief.

How do I establish a consistent visual direction before starting UI design?

You establish a consistent visual direction by interviewing stakeholders about brand personality, audience, and UI constraints, which produces an operational north star for downstream UI skills.

Can I generate a design brief if I already have existing CSS tokens and config artifacts?

Yes, the process reads existing context first, checking for partially implemented tokens, CSS artifacts, and prior screenshots to avoid re-asking design decisions already made in the codebase.

What should be included in a UI design brief to align downstream UX skills?

A UI design brief should include Decisions Made, Ruled Out options, and Open Questions so downstream skills handling tokens, animation, and landing pages can act consistently.

When do I need a guided interview for UX design planning?

You need a guided interview for UX design planning when starting a new product UI or when existing design decisions are ambiguous and contradictory across screens, tokens, and motion.