---
name: figma-design-brief-generator
description: "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 open Figma with fewer questions. 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."
---

# Figma Design Brief Generator

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 open Figma with fewer questions.

## When to use

Use this skill 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 it for a full product requirements document, a visual critique, or engineering specs.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. State the problem and audience from the inputs and write goals that can be tested and non-goals that limit scope.
3. Write the key user flows as numbered steps and derive the screens needed for each platform chosen.
4. List the states for each screen (empty, loading, error) when the toggle is on.
5. Add content and copy needs and the accessibility must-haves that fit the platforms.
6. Write a definition of done matched to the fidelity chosen and close with three open questions for the designer.

## Inputs

- **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)

## Output

A structured brief with the eight fixed sections in order, ending with three open questions for the designer.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Figma Design Brief Generator

Write a design brief for this piece of work.

- What is being designed: {{What is being designed}}
- Platform: {{Platform}}
- The user problem: {{The user problem}}
- Success looks like: {{Success looks like}}
- Constraints: {{Constraints}}
- Fidelity needed: {{Fidelity needed}}
- List every empty or loading or error state to cover: {{List every empty or loading or error state to cover}}

Structure the brief as: problem, audience, goals and non-goals, key user flows as numbered steps, required screens and states, content and copy needs, accessibility must-haves, and a definition of done. Make the goals testable and the non-goals explicit so scope is clear.

When the state toggle is on, list every empty, loading, and error state per screen. Match the screen list to the platforms and fidelity chosen. Close with three open questions the designer should resolve before opening Figma.

## Pitfalls

- 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.
