Product Design Intake
Establish user task, content, constraints, brand direction, risk, and measurable outcomes before frontend design work.
SKILL.mdskills/frontend/design/product-design-intake/SKILL.md
GitHubProduct Design Intake
Purpose
Prevent invented users, policy, content, visual identity, and success metrics from driving implementation.
When to Use
- A new page, flow, or component family lacks a trusted current brief.
- A redesign could change behavior, hierarchy, conversion, or user familiarity.
Do
- Identify primary task, completion signal, consequence of failure, entry point, recovery path, and real content extremes.
- Capture device, locale, accessibility, security, performance, brand, and existing-pattern constraints.
- State assumptions and write testable acceptance criteria before choosing layout.
Do Not
- Do not create fictional personas, choose patterns from a gallery, or use final hierarchy based on placeholder content.
- Do not treat a screenshot as a substitute for task and state decisions.
Review Checklist
- Primary task and completion signal are one clear statement.
- Failure, recovery, content, accessibility, and device constraints are known.
- Brand direction and anti-direction are documented.
Expected Output
- One-page product brief.
- Task-flow and state inventory.
- Assumption register and acceptance criteria.