stitch-landinglisted

# stitch-landing End-to-end skill that takes a project (README + screenshots) and ships a deployed landing page on GitHub Pages, using Stitch MCP for the design pass and Tailwind CDN for the production output. ## When to use - User has a repo with a README and asks for a landing page hosted on GitHub Pages. - User says "use Stitch to design", or wants a marketing/preview page they can share. - Project already has screenshots, badges, or feature copy in the README that should be reused (don't rewrite copy — port it). ## When NOT to use - The project already has a Pages site you'd be overwriting — confirm first. - The user wants a multi-page docs site (use Docusaurus / MkDocs / Astro instead). - The repo has no README and no clear positioning — run discovery first. ## Required tools - **Stitch MCP** — `mcp__stitch__create_project`, `mcp__stitch__generate_screen_from_text`, `mcp__stitch__list_screens` (Stitch MCP server installed and authenticated). - **gh CLI** — authenticated for the target repo's owner. - **git** — push access to the target repo's default branch (or fallback to PR flow). - **curl** — to download Stitch's HTML output and verify the live URL. ## The flow (8 phases) ### Phase 1 — Read the repo Read `README.md`, `LICENSE`, screenshots in `docs/`, and any existing `index.html`. Extract: - **Positioning** — the one-line tagline (usually the README's first blockquote or H1 subhead). - **Value props** — bullet-list features under "Why" / "Features" / "High