Writing a spec

Include

• Who it is for and the one job to be done
• Screens (named) and what each one does
• Data that must persist, and where (local vs account)
• Empty, error, and first-run states
• What is explicitly out of scope

Cut

• Slogans. "Seamless", "unlock", "elevate" waste tokens.
• Unbounded scope. Phase 1 should ship in one sitting.
• Fake citations and invented APIs.

Shape

Start with "Build a …" then constraints. End with the visual direction (this catalog prefers phosphor-on-paper terminal, not neon).