What is astro conversion kit?
Astro Conversion Kit is a set of Agent Skills that guides a coding agent through converting a live website into a static Astro site. It is designed primarily for WordPress sites and also works with other sites served over HTTP. The agent captures the existing site, builds the Astro version, checks it against the original, and prepares a pull request, staging deploy, and launch runbook. It works with Claude Code, Codex, and other agents that read SKILL.md.
astro conversion kit Features:
Agent Workflow: The skills run in a coding agent that can execute shell commands, ask a single intake message about the repository, hosting, and forms, then proceed using stated defaults.
Read-Only Capture: A paced crawl collects rendered HTML, page metadata, redirects, media, fonts, feeds, and screenshots from sitemaps, WordPress REST endpoints, and links between pages.
Astro Build: The kit creates a new Astro repository and builds layouts and pages from captured markup, retaining media paths and pruning captured CSS according to coverage.
Parity Gates: Automated checks compare routes, redirects, SEO tags, visible text, links, media, sitemaps, feeds, forms, and scripts with the captured baseline.
Visual Review: The workflow compares screenshots and computed styles at 390, 768, and 1440 pixels, then reviews every page at 390 and 1440 pixels.
WordPress Handling: The conversion accounts for public pages and posts, resized image files, theme styles, shortlinks, category collisions, forms, third-party scripts, and existing redirects.
Launch Handoff: A run produces a pull request, noindexed staging deploy, verification command, suggestions report, contact sheets, and host-specific launch runbook, with post-launch checks for 30 days.
astro conversion kit Benefits:
Fewer Manual Checks: Captured baselines and repeatable gates make it easier to spot missing pages, metadata, media, or redirects without manually comparing each item.
Safer Review: The work stays on an astro-rebuild branch and reaches main through a pull request, leaving the merge and launch under your control.
Preserved Discoverability: Checking URLs, titles, descriptions, canonicals, structured data, and redirects helps retain important search and sharing signals during a rebuild.
Clearer Decisions: The plan records templates, counts, media choices, and unusual cases, while the suggestions report separates proposed improvements from changes made.
Less Server Maintenance: The result is a static site without PHP or an application server running on the hosting server, reducing the runtime components to maintain there.
Use Cases:
WordPress Migration: Move a public WordPress site to Astro while checking that its pages, posts, URL structure, resized images, and redirects remain represented.
Theme Rebuild: Recreate a classic, page-builder, or block-theme site in Astro and compare its appearance across desktop, tablet, and mobile widths.
Marketing Site Move: Convert a public marketing site served over HTTP when the team wants a static Astro build and can review a pull request before launch.
Pre-Launch Review: Check a proposed rebuild on a noindexed staging deployment, review detected issues, and follow a runbook before changing production.
Static-Site Scoping: Assess a site with search, comments, carts, logins, or user-generated content and identify which functions need a third-party embed or separate arrangement.

