Mobile Wireframe
Define the screen skeleton and interaction hierarchy without choosing colors, typography, imagery, or decorative style.
Establish the input contract
Prefer ux-architecture.json plus product-brief.json. Validate upstream artifacts when validators exist. Preserve upstream Requirement, Flow, Screen, and State IDs. If the architecture is incomplete, record the gap rather than inventing a polished screen.
Build the wireframe
For each screen:
- State the single user question and primary task.
- Order the safe-area, navigation, context, content, action, and feedback regions.
- Assign each region a semantic role, content pressure, component role, and state behavior.
- Mark fixed, scrollable, sticky, keyboard-avoiding, sheet, dialog, and system-handoff behavior.
- Map entry, exit, primary action, secondary actions, and interruption recovery.
- Cover every upstream state; distinguish state changes from new screens.
Use neutral boxes and labels in visual artifacts. A wireframe may specify hierarchy, density, copy length, and interaction intent, but must not pretend to establish final tokens or visual direction.
Check the core flow
Trace at least one critical before/during/after path and one failure or interruption path. Verify that the primary action remains reachable, content identity survives errors, destructive actions have a consequence boundary, and system surfaces have in-app fallbacks.
Read references/wireframe-rules.md before finalizing regions and references/wireframe-schema.md before creating JSON.
Produce and validate
Create:
wireframe.mdusing assets/wireframe-template.md.wireframe.jsonusing assets/wireframe-template.json.
Run python3 scripts/validate_wireframe.py <path-to-wireframe.json> and fix every error. When an upstream UX file is available, also run python3 scripts/validate_wireframe.py <path-to-wireframe.json> --source-ux <path-to-ux-architecture.json> to check screen and state coverage.
Enforce the output order
- Source contract and assumptions.
- Navigation and flow skeleton.
- Screen inventory and region contracts.
- State, overlay, keyboard, and system-surface behavior.
- Traceability and unresolved decisions.
Do not finish with a styled mockup disguised as a wireframe or with a screen inventory that omits states and recovery.


