design-brief

Create a design brief through interactive interview and codebase exploration.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill design-brief-yashmishra2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-brief
Source: https://github.com/yashmishra2006/LexWrite-Website/tree/main/.agents/skills/design-brief
Command: npx skills add https://github.com/yashmishra2006/LexWrite-Website --skill design-brief-yashmishra2006

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new feature or page without a clear design direction leads to inconsistent UI, scope creep, and rework. This Skill produces a structured design brief that captures the problem, experience principles, aesthetic direction, and component inventory before any code is written. ## Core Features & Use Cases - Structured Interview Process: Walks through user goals, emotional tone, constraints, and content requirements with recommended answers for each question. - Codebase Exploration: Scans for CSS tokens, Tailwind config, UI framework themes, component directories, and font loading so the brief extends existing patterns instead of replacing them. - Standardized Output Template: Saves a complete brief covering problem, solution, experience principles, component inventory, key interactions, responsive behavior, accessibility, and out-of-scope items to .design/<feature-slug>/DESIGN_BRIEF.md. - Use Case: Before building a new settings page, run the interview to define the direction, then hand the resulting brief to downstream design and implementation steps. ## Quick Start Ask the assistant to write a design brief for the feature or page you want to plan, such as the onboarding flow.

Frequently Asked Questions about design-brief

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

FAQPage Schema
How do I write a design brief for a new feature?

Describe what you want to build, who it is for, and any constraints. The skill interviews you about users, tone, references, and content, explores your codebase for existing patterns, then writes a structured brief to .design/<feature-slug>/DESIGN_BRIEF.md.

What should a design brief include before building a UI?

A brief should cover the user problem, solution experience, experience principles, aesthetic direction, existing patterns, component inventory, key interactions, responsive behavior, accessibility requirements, and explicit out-of-scope items.

Does the design brief use my existing Tailwind or component setup?

Yes. The process scans for tailwind.config files, CSS variables, UI framework themes like Material UI or Chakra, component directories, and font loading so the brief extends your current design system rather than replacing it.

Where is the design brief file saved?

Each brief is saved to .design/<feature-slug>/DESIGN_BRIEF.md, where the slug is a lowercase hyphenated name like onboarding-flow. This keeps briefs for different features separate so repeated runs never overwrite previous work.

When should I not use a design brief?

Skip the brief for trivial changes like copy edits or single-component tweaks where no design decisions are involved. The interview process is meant for new features, pages, or UI directions with unresolved questions.