astro-conversion plugin
Convert a WordPress site (or any live site) into a static Astro site with URL, content, SEO and visual parity gates, then launch it safely.
How to install the astro-conversion plugin
Run both commands inside Claude Code. The first adds the marketplace once; the second installs the plugin.
/plugin marketplace add ethanplusai/astro-conversion-kit
/plugin install astro-conversion@astro-conversion-kitWhat's inside astro-conversion
8 parts read from the plugin's own files.
Skills 8
Claude loads it when the task matches- capture-site
Crawl a live website, read-only and paced, into a capture/ folder that a rebuild is checked against — every page's HTML, text and head tags, redirects with every hop, links, third-party scripts, the media set, stylesheets, fonts, logo and icons, feeds, templates, and live screenshots at three widths. Use before converting or rebuilding a site, when asked to crawl, capture, snapshot or inventory a site, or when a capture stopped on blocks and needs resuming.
- convert-site
Convert a live website (WordPress first; Drupal, Webflow, Squarespace, Wix and static sites too) into a static Astro site with the same URLs, content, head tags, media, redirects and look, proven by parity gates and a pixel-level visual review, ending in one pull request, a noindexed staging deploy and a launch runbook. Use when asked to convert, rebuild, migrate or clone a site to Astro, when handed a site URL with this kit's link, to resume a conversion from .conversion/state.json, or with --apply <id> to apply one suggestion as a proposal.
- launch-audit
No description in the file.
- parity-gates
Freeze a site capture into baseline/ and prove an Astro build matches it — every route, redirect (one hop, through a simulation of the host), SEO head field, visible text, internal link, media file, sitemap entry, feed, form, third-party script and security header — with approved differences in exceptions.json and improvements in proposals.json. Use after a capture to build the baseline, when compiling redirects.csv for Vercel or Cloudflare, before calling any conversion page done, when a gate fails and needs reading, or to check a staging deploy against the baseline.
- post-launch
The moment DNS moves and for the thirty days after — verifies the cutover (DNS propagation, certificate, http and www redirects, the noindex, robots and sitemap on the live host, every redirect the audit mapped, forms, analytics, the staging copy, the old host, security headers), diffs production against the pre-launch baseline, and schedules the watch. Use when asked did the launch work, is the site live, what should I check after launch, the domain just switched, or when a site went live in the last month and something looks wrong. It is read-only and exits 0 whatever it finds.
- pre-launch
Gate a website launch from its repository — repo hygiene, placeholders and leaked dev hosts, the production build, the build output (404 page, internal references, icons, social cards, robots, sitemap, canonicals, titles, headings), framework configuration, and redirect coverage for the site being replaced — then walk the human checklist no script can verify. Use before any site launch, before a DNS cutover, when a site is replacing an existing one, or when somebody asks whether a site is ready to launch. Read-only apart from its own report and a progress file; it exits 1 if anything fails.
- suggest-improvements
List what is worth fixing on a site the conversion reproduced as-is — SEO, content, links, accessibility, performance, security, analytics and design — each item with its path, evidence, effort, risk and whether it can be applied mechanically, plus the agent's own design and content observations. Use after the parity gates and the visual review are green and before the pull request, or when someone asks what could be better on the converted site. It changes nothing.
- visual-review
Prove an Astro rebuild looks like the live site it replaces — full-page screenshots of both sides with motion frozen, a pixel diff with a 0.5 % pass line, a computed-style comparison of typography, colour and spacing, and one contact sheet to look at every pair. Use after a template is built, before calling a conversion page done, when someone asks whether the new site matches the old one, or when a diff or style row fails and needs fixing.
Using astro-conversion in Claude Code
Skills need no command. Claude reads them when your request matches what they describe.
Update, turn off or remove
- Update the plugin (shell)
- claude plugin update astro-conversion@astro-conversion-kit
- Refresh the marketplace
- /plugin marketplace update astro-conversion-kit
- Turn it off for now
- /plugin disable astro-conversion@astro-conversion-kit
- Remove it
- /plugin uninstall astro-conversion@astro-conversion-kit
Skills in astro-conversion
- capture-siteethanplusai/astro-conversion-kit
Crawl a live website, read-only and paced, into a capture/ folder that a rebuild is checked against — every page's HTML, text and head tags, redirects with every hop, links, third-party scripts, the media set, stylesheets, fonts, logo and icons, feeds, templates, and live screenshots at three widths. Use before converting or rebuilding a site, when asked to crawl, capture, snapshot or inventory a site, or when a capture stopped on blocks and needs resuming.
23 files132stars - convert-siteethanplusai/astro-conversion-kit
Convert a live website (WordPress first; Drupal, Webflow, Squarespace, Wix and static sites too) into a static Astro site with the same URLs, content, head tags, media, redirects and look, proven by parity gates and a pixel-level visual review, ending in one pull request, a noindexed staging deploy and a launch runbook. Use when asked to convert, rebuild, migrate or clone a site to Astro, when handed a site URL with this kit's link, to resume a conversion from .conversion/state.json, or with --apply <id> to apply one suggestion as a proposal.
34 files132stars - parity-gatesethanplusai/astro-conversion-kit
Freeze a site capture into baseline/ and prove an Astro build matches it — every route, redirect (one hop, through a simulation of the host), SEO head field, visible text, internal link, media file, sitemap entry, feed, form, third-party script and security header — with approved differences in exceptions.json and improvements in proposals.json. Use after a capture to build the baseline, when compiling redirects.csv for Vercel or Cloudflare, before calling any conversion page done, when a gate fails and needs reading, or to check a staging deploy against the baseline.
32 files132stars - post-launchethanplusai/astro-conversion-kit
The moment DNS moves and for the thirty days after — verifies the cutover (DNS propagation, certificate, http and www redirects, the noindex, robots and sitemap on the live host, every redirect the audit mapped, forms, analytics, the staging copy, the old host, security headers), diffs production against the pre-launch baseline, and schedules the watch. Use when asked did the launch work, is the site live, what should I check after launch, the domain just switched, or when a site went live in the last month and something looks wrong. It is read-only and exits 0 whatever it finds.
10 files132stars - pre-launchethanplusai/astro-conversion-kit
Gate a website launch from its repository — repo hygiene, placeholders and leaked dev hosts, the production build, the build output (404 page, internal references, icons, social cards, robots, sitemap, canonicals, titles, headings), framework configuration, and redirect coverage for the site being replaced — then walk the human checklist no script can verify. Use before any site launch, before a DNS cutover, when a site is replacing an existing one, or when somebody asks whether a site is ready to launch. Read-only apart from its own report and a progress file; it exits 1 if anything fails.
16 files132stars - suggest-improvementsethanplusai/astro-conversion-kit
List what is worth fixing on a site the conversion reproduced as-is — SEO, content, links, accessibility, performance, security, analytics and design — each item with its path, evidence, effort, risk and whether it can be applied mechanically, plus the agent's own design and content observations. Use after the parity gates and the visual review are green and before the pull request, or when someone asks what could be better on the converted site. It changes nothing.
32 files132stars - visual-reviewethanplusai/astro-conversion-kit
Prove an Astro rebuild looks like the live site it replaces — full-page screenshots of both sides with motion frozen, a pixel diff with a 0.5 % pass line, a computed-style comparison of typography, colour and spacing, and one contact sheet to look at every pair. Use after a template is built, before calling a conversion page done, when someone asks whether the new site matches the old one, or when a diff or style row fails and needs fixing.
13 files132stars
astro-conversion plugin questions
How do I install the astro-conversion plugin?
In Claude Code run /plugin marketplace add ethanplusai/astro-conversion-kit, then /plugin install astro-conversion@astro-conversion-kit.
What does the astro-conversion plugin include?
astro-conversion bundles 8 skills.
How do I update or remove the astro-conversion plugin?
Update it with claude plugin update astro-conversion@astro-conversion-kit in your shell, or from the Installed tab of /plugin. Remove it with /plugin uninstall astro-conversion@astro-conversion-kit.