Skip to content
UX Atlas
AI workflowCraft conventionIntermediate

Feature Idea to UX Specification

Expanding a rough idea into a structured specification, which is mainly useful as a completeness check.

Definition

Given a feature description, a model can produce a structured specification covering states, edge cases, accessibility requirements and open questions. It is a scaffold to edit, not a document to publish.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. Prompt
  3. Continue from here

Prompt

text
Expand this feature idea into a UX specification.

Feature: [description]
Users: [who, expertise, context]
Platform: [web, iOS, Android, desktop]
Existing conventions: [components and patterns already in the product]

Cover:
- User goal, stated without reference to the solution
- Entry points
- The main flow, as steps
- Every state: empty, loading, partial, error, success, offline
- Edge cases: long content, zero items, maximum items, permissions denied
- Accessibility requirements: keyboard, screen reader, focus, labelling
- Content: every string the interface needs
- Open questions requiring a product decision

Flag anything you inferred rather than were told.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Often used with

These usually appear in the same screen or the same decision.

Related concept

Connected closely enough to change how you apply this.