April 2, 2026
Tutorial
4 min read
Ship a Website in 60 Seconds
Install AcePilot. Open Claude Code. Type one word. Watch 6 specialist
agents build a complete landing page with pricing, SEO, analytics, and
security review. Here's exactly how.
What you'll get
By the end of this tutorial, you'll have a production-ready landing page
with:
- Hero section with value prop, CTA, and install snippet
- Feature grid, pricing tiers (3-tier with annual toggle), and FAQ
- SEO: meta tags, Open Graph, JSON-LD structured data, sitemap
- Analytics: Plausible or PostHog event tracking on all CTAs
- Security review: XSS prevention, CSP headers, mixed content check
- Mobile responsive, dark theme, accessible
All generated autonomously. No templates. No boilerplate. One command.
Prerequisites
- Claude Code installed and working
- A terminal (macOS, Linux, or WSL)
- Git (for checkpoints)
The steps
Install AcePilot
Two commands. Takes about 30 seconds.
$ git clone https://github.com/acepilot-app/acepilot.git
$ ./acepilot-14.0/install.sh
Installing AcePilot 14.0 — Human Handoff
✓ CLAUDE.md (trigger)
✓ settings.json (permissions + status line)
✓ commands/acepilot.md (the brain)
✓ agents/researcher.md (Haiku scanner)
✓ agents/reviewer.md (code reviewer)
✓ agents/designer.md (UX + accessibility)
✓ agents/security.md (vulnerability scanner)
✓ agents/architect.md (architecture + performance)
✓ agents/strategist.md (product + growth)
✓ 3 free Pro sessions included
Done.
Create a project
Make a directory. Initialize git. Open Claude Code.
$ mkdir my-product && cd my-product && git init
$ claude
Say the magic word
Type /acepilot god website and let go of the keyboard.
That's it. AcePilot takes over.
> /acepilot god website
GOD MODE. 8 tasks. Smart dispatch. Zero stops.
ORIENT: new project, no existing files. Archetype: static site.
IDENTITY: developer tool, dark theme, monospace, direct copy.
REVENUE: freemium, 3-tier pricing ($0/$29/$79).
[1/8] ✓ site/index.html — landing page with hero, features, pricing
@designer: PASS @strategist: 2🟡 (CTA copy, pricing anchor)
[2/8] ✓ site/robots.txt — search engine crawl rules
[3/8] ✓ site/sitemap.xml — 3 pages mapped
[4/8] ✓ site/blog/index.html — blog scaffold
[5/8] ✓ site/compare/vs-cursor.html — comparison page
[6/8] ✓ site/badge/index.html — embed badge system
[7/8] ✓ .github/workflows/ci.yml — deploy pipeline
[8/8] ✓ README.md — quickstart + screenshot
GOD MODE COMPLETE. 8 done, 0 blocked.
Ready to push. Branch: feat/website
Review and deploy
AcePilot committed every task as a buildable checkpoint. Review the
diff, push the branch, and your CI/CD handles the rest.
$ git log --oneline
a1b2c3d acepilot: readme quickstart + screenshot
d4e5f6g acepilot: deploy pipeline
...
h7i8j9k acepilot: landing page with hero, features, pricing
What happened behind the scenes? AcePilot's Directive
Expansion Engine classified your one-word directive into a full business
spec. It decided the archetype (static site), revenue model (freemium),
identity (dark theme, developer aesthetic), conversion strategy (CTA
above fold, 3-tier pricing), and tech stack (single HTML+CSS, zero deps).
Then 6 specialist agents reviewed every task: @designer checked UX and
accessibility, @security scanned for vulnerabilities, @strategist
optimized conversion, @reviewer verified code quality.
What if you want more control?
God mode makes every decision autonomously. If you want to review the
plan first, use plan mode instead:
> /acepilot plan website
Or use auto mode for autonomous execution that asks
before pushing:
> /acepilot auto website
Next session: it's faster
AcePilot captured a playbook from this session. Next
time you say "website" in any project, it replays the proven workflow
instead of re-deriving everything. Session 1 figures it out. Session 10
runs it from memory.
The self-calibration engine also recorded specialist precision and cycle
times. After 10 sessions, AcePilot automatically adjusts its routing,
gates, and ceremony tiers based on what worked.
Try it now
30-second install. 3 free god mode sessions. No credit card.
Install AcePilot
Back to blog ·
Why AcePilot Exists