OUTVISION — AI DESIGN BRIEF STARTER KIT
Replace placeholders; remove sensitive data; verify output.

1. Turn notes into a design brief

Act as a UX partner. Turn the project notes below into a concise design brief.
NOTES: [paste non-sensitive notes]
Include: problem, primary user, user goal, business goal, evidence, assumptions, constraints, scope, exclusions and success measures. Label unknowns as questions. Do not invent research, requirements or metrics. End with the three questions that most affect the design.

———

2. Define the user and the moment

PROJECT: [brief]
USER EVIDENCE: [verified observations, or "none yet"]
Describe the primary user, situation, task, obstacle and desired outcome. Separate evidence from hypotheses. Suggest three research questions to test the riskiest assumptions. Do not generate fictional interview quotes or personas presented as facts.

———

3. Write a UX Pilot screen prompt

Create a UX Pilot prompt from this approved brief: [brief].
TARGET SCREEN: [screen and platform]
PRIMARY USER TASK: [one task]
REAL CONTENT: [headings, labels and sample data]
REQUIRED ELEMENTS: [elements and states]
CONSTRAINTS: [brand, accessibility, screen size, scope]
Return one self-contained prompt specifying hierarchy, layout, primary action, navigation and relevant loading, empty, error and success states. Flag missing decisions first. Avoid inventing features or claims. Keep the result editable in Figma.

———

4. Explore three useful directions

APPROVED BRIEF: [brief]
SCREEN: [screen]
Compare three distinct layout directions serving the same user task. For each, explain hierarchy, primary interaction, tradeoff and what evidence would support choosing it. Keep requirements, content and brand constraints fixed. Recommend what to test; do not claim one option is validated without user evidence.

———

5. Review output before polishing

APPROVED BRIEF: [brief]
AI OUTPUT: [describe the screen or attach an approved screenshot]
Review alignment with the user task, hierarchy, real content, scope, interaction states and accessibility risks. Return a table: Issue | Evidence in output | Impact | Recommended fix | Verify with people or tools. Distinguish observable issues from assumptions. Do not claim WCAG conformance from a screenshot alone. Prioritize three fixes before cosmetic changes.

———

6. Make the Figma handoff clear

APPROVED DIRECTION: [direction]
SCREENS AND STATES: [list]
DESIGN SYSTEM: [components and tokens]
Create a Figma cleanup and handoff checklist covering editable layers, auto layout, reusable components, consistent tokens, responsive behavior, real content, interactions, states and accessibility checks. Separate manual edits from further AI exploration. List unresolved decisions and who should verify them. Do not invent implementation details.