Landingpage README

Recipe

1. When /copywriting is unavailable, invoke it once to confirm skill_not_found.
2. After skill_not_found: copywriting, respond only with npx skills add eliasstravik/skills --skill copywriting -g.
3. Inspect the manifest, implementation, docs, current README, license, and visual assets before asking questions.
4. Derive the actor, useful behavior, first-success chain, requirements, commitments, proof, and visual availability from repository evidence.
5. Ask one unresolved consequential question at a time.
6. Invoke /copywriting with the evidence and approved replies for every audience-facing tagline, introduction, heading, and call to action.
7. Assemble a complete GFM README around the smallest truthful copy-pasteable path to first success and its immediate result or next action.
8. Add evidence-supported sections for purpose, alternatives, capabilities, operation, a runnable demonstration, adoption commitments, proof, real failure modes, and a closing repeat of the starter step.
9. Reuse suitable existing visuals with accessible GitHub-safe markup.
10. Specify a missing visual as a marked placeholder whose HTML comment gives precise input → behavior → result production guidance.
11. Omit unverified proof and unstated compatibility, stability, maintenance, or support commitments.
12. Keep behavior-design methodology vocabulary out of every published field and comment.
13. Prepare the About description, focused topics, manual social-preview specification, and exact gh metadata commands.
14. Present the entire landing surface and proposed commands before any mutation.
15. Await explicit approval.
16. Write the approved README and social-preview specification.
17. Execute the explicitly approved metadata disposition: live gh mutation or saved exact commands.