First-screen checklist
- State the user and outcome fast. A new visitor should know who the project is for and what it helps them do inside the first few lines.
- Lead with payoff before architecture. Category terms and abstractions belong after the reader understands why the project exists.
- Show one obvious next action. Choose one: install, demo, signup, or example run. Do not make the first action ambiguous.
- Cut internal language. Replace maintainer shorthand and feature fragments with buyer-facing language first.
- Keep proof close. Put a screenshot, demo link, short example, or credible usage clue near the opening instead of burying it.