Figma Design Brief Generator skill for Claude and Codex
Writes a design brief with the problem, goals, flows, screens and states, copy needs, accessibility must-haves, and a definition of done, so a designer can…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a product manager or founder needs to brief a designer on a screen or flow with goals, constraints, states, and a definition of done. Do not use for a full product requirements document, a visual critique, or engineering specs. Related topics: Design, Planning, Communication.
What it will ask you for
- What is being designed (free text, e.g. "Onboarding flow or pricing page or settings screen")
- Platform (choose any: Web desktop, Web mobile, iOS, Android, Email)
- The user problem (longer free text)
- Success looks like (free text, e.g. "The measurable or observable outcome")
- Constraints (longer free text)
- Fidelity needed (choose one: Wireframes, Hi-fi mockups, Interactive prototype, Production-ready specs)
- List every empty or loading or error state to cover (choose one: Yes, No)
How it works
- State the problem and audience from the inputs and write goals that can be tested and non-goals that limit scope.
- Write the key user flows as numbered steps and derive the screens needed for each platform chosen.
- List the states for each screen (empty, loading, error) when the toggle is on.
- Add content and copy needs and the accessibility must-haves that fit the platforms.
- Write a definition of done matched to the fidelity chosen and close with three open questions for the designer.
What you get
A structured brief with the eight fixed sections in order, ending with three open questions for the designer.
What it watches out for
- Writing goals as features (add a progress bar) instead of outcomes the design can be judged on.
- Skipping error and empty states, which then get designed by developers at the last minute.
- Asking for high fidelity when the flow itself is not yet agreed.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.