astro-conversion-kit

astro-conversion-kit is an open-source set of Agent Skills published by ethanplusai that lets a coding agent convert a WordPress site, or any site served over HTTP, into a static Astro site. A run ends with a pull request, a noindexed staging deploy and a launch runbook. It works in Claude Code, Codex or any agent that reads SKILL.md.

What It Is

The kit is a migration workflow packaged as Agent Skills, with plain Node scripts handling the steps that must be exact. The goal is a rebuilt site with the same URLs, content, titles, descriptions, canonicals, structured data, media paths and redirects, and a design checked pixel by pixel at 390, 768 and 1440 px. Because capture reads rendered HTML, it needs no admin login, plugin or database export. WordPress is the first-class case.

How a Conversion Runs

The README describes eight phases: intake, capture, plan, scaffold and baseline, build, gates, visual review, and launch checks.

• Intake fingerprints the platform and asks one message of questions, each with a stated default.
• Capture is a paced, read-only crawl using sitemaps, the WordPress REST API and links. It saves HTML, head tags, redirects, media lists, fonts, feeds and screenshots.
• The build works on an astro-rebuild branch, reuses captured markup and pruned CSS, and keeps media at original paths.
• Gates check routes, redirects, SEO tags, visible text, links, media, sitemap, feeds, forms and scripts against a frozen baseline on every commit.
• Visual review pixel-diffs live and new screenshots per template at three widths.

Outputs and Handover

The run produces a pull request into a repo you own, a noindexed staging deploy on Vercel or Cloudflare Pages, contact sheets of live, new and diff screenshots, a suggestions report, and a launch runbook. The new repo includes an npm run verify command so the gates keep working after the old site is gone. The default build reproduces the live site as is, and fixes are proposals you approve.

Scope and Limits

Static sites cannot do site search, comments, carts, logins or user-generated content. The kit flags these at intake as out of scope and offers options such as a third-party embed or keeping that part on a subdomain. It refuses to run on end-of-life Node, submit forms or log in on the live site, touch DNS, or commit anything but the scaffold to main. It handles one site per run, and macOS or Linux is required.

Setup Path

Paste a prompt naming your site and the repository into your coding agent, or install the skills with npx skills add or the Claude Code plugin marketplace. Cloning the repo also allows running scripts by hand, and a preflight script reports which required tools are installed. The README reports averages from 45 WordPress conversions, including an average run time of 83 minutes.