A companion to “It’s Not a File. It’s a Conversation.”

Everything to check before you ship the file—or yourself—into dev purgatory.

🧱 01. Page Structure

• [ ] File starts on a cover page (with project name, date, context)
• [ ] Pages follow a clear sequence (e.g., Cover → Flow → Screens → Components → Dev Notes)
• [ ] Each page is titled clearly with consistent naming

🔁 02. Flow & Navigation

• [ ] Frame order matches user flow
• [ ] Flow arrows are directional and don’t cross over unnecessarily
• [ ] Dead ends or ambiguous branches are labeled or commented
• [ ] Alternate or edge cases are included (empty state, error, success)

🗒 03. Annotations

• [ ] All major UI elements have callouts (tooltips, icons, inputs, nav, etc.)
• [ ] Motion and interactions are explained (especially non-obvious ones)
• [ ] Design decisions or trade-offs are briefly noted where relevant