create-website
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (POSITIONING.md, WEBSITE.md, DESIGN.md, CREATE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new website or land
npx skills add wondelai/skills --skill create-website --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guided journey from a blank page to a live, high-converting website through ten phases run in a dependency-respecting order: message, then design, then conversion, then a brutal review. The agent asks before every decision and never designs before the message is settled, and artifacts are stored in the docs/ folder. It orchestrates ten skills in sequence and resumes across sessions.
How it works
- Reads and summarizes the current plan from docs/CREATE-WEBSITE-PLAN.md and existing artifacts, then asks which phase to enter.
- On first run, performs Intake to create the tracker with phase statuses (pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason).
- For each phase, announces its purpose, required decisions, produced artifact, and rough effort; offers proceed / skip / defer; marks the phase in-progress when proceeding.
- Invokes the phase’s skill by its slug (e.g., one-page-marketing, storybrand-messaging, made-to-stick, etc.). If a skill is unavailable, suggests installing via
npx skills add wondelai/skills/<slug> --global. - During a phase, asks all decision questions under Decide with the user, records choices in the tracker as Key Decisions.
- At phase exit, presents draft artifact content for sign-off; upon approval, writes or extends docs/ files (UPPERCASE in docs/), updates tracker status and next actions.
- Ensures artifacts come from templates and are extended rather than overwritten; maintains strict documentation in the docs/ folder.
When to use it
Use when the user wants to build a new website or landing page from scratch, or turn a validated idea into a page that converts. Can also guide improvements to an existing site by invoking relevant phases (e.g., improve-website, grow-website) or switch to create-app for software products.
What it can touch
- Creates/extends docs folder files in ALL CAPS (e.g., MARKETING.md, POSITIONING.md, WEBSITE.md, DESIGN.md, CREATE-WEBSITE-PLAN.md).
- Updates the tracker with phase statuses and Key Decisions.
- Invokes skills by slug, such as
one-page-marketing,storybrand-messaging,made-to-stick,top-design,web-typography,refactoring-ui,ux-heuristics,cro-methodology,scorecard-marketing,steve-jobs-design-review.
Caveats
- Requires the availability of listed skills; if unavailable, instructs user to install via npm-like command. Status and progress are stored in project docs to enable resumability across sessions. The process emphasizes messaging first, design second, and conversion last; phase can be deferred if marked GATE. No guarantees about outcomes are stated beyond phase artifacts and sign-offs.
# Create a Website A blank page becomes a live, high-converting website through ten phases run in one dependency-respecting order: message, then design, then conversion, then a brutal review. This journey is interactive — the agent asks before every decision and never designs before the message is settled — and resumable, because every decision and artifact lives in the project's `docs/` folder. You drive the phases; the constituent skills carry the method. ## Core Principle **Message before design, design before conversion — in that order; looks-fine is the floor, not the goal.** A visitor decides in five seconds whether to stay, and that decision rides on whether they instantly understand what you do and why it matters to *them* — so clarity comes first and design serves it. This skill sequences the phases, asks the questions, and records the decisions; the constituent skills carry the frameworks. Invoke them rather than improvising their method. ## Journey Map | Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | one-page-marketing | Who is this for, and what is the site's one job? | Creates docs/MARKETING.md; extends docs/CUSTOMER.md | | 2 | storybrand-mess
- Core Principle
- Journey Map
- Operating Rules
- Intake
- Phases
- Phase 1 — Frame the strategy and pick one niche (one-page-marketing)
- Phase 2 — Write the message with StoryBrand (storybrand-messaging)
- Phase 3 — Make the message stick (made-to-stick)
- Phase 4 — Design the signature moment (top-design)
- Phase 5 — Choose and tune the type (web-typography)
- Phase 6 — Make it systematic (refactoring-ui)
- Phase 7 — Make it effortless to use (ux-heuristics)
- Phase 8 — Engineer the conversion (cro-methodology)
- Phase 9 — Add a lead-generating quiz (scorecard-marketing)
What does the create-website skill do?
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (POSITIONING.md, WEBSITE.md, DESIGN.md, CREATE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new website or land
How do I install it?
Run `npx skills add wondelai/skills --skill create-website --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wondelai/skills, a repository with 1,835 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.