story-directionlisted

# Story direction Every other skill here executes a decision. This one makes it. `frontend-craft` gets as far as a visual direction — a stance about type, colour and density. That is not the same as knowing what the page *says*, in what order, and why anyone should still be reading at the fourth section. A page assembled section by section, each one competently designed, arrives looking like a list of components. A page directed is a sequence that goes somewhere. You are the director. Do this before you choose a typeface, and long before you generate anything. ## 1. Find the argument Write the page's claim in one sentence, in your own words, without adjectives. Not "a modern site for a design studio" — that is a category, not a claim. Something a reader could disagree with: *"most brands stop being good at the handover"*, *"your ledger is lying to you by month"*. If you cannot write that sentence, you do not yet know what you are building, and no amount of layout will hide it. Ask, or state the claim you are assuming in `assumptions` and proceed on it. ## 2. Break the claim into beats A beat is a section with a job. Name the job before the content: | Beat | Its job | |---|---| | 1 | make the claim, and make it cost something to disagree | | 2 | show you have earned the right to say it | | 3 | make it concrete — the thing itself | | 4 | remove the last objection | | 5 | ask | Three to six beats. The classical shape is tension, then exploration, then resolution, and i