iOSDevSK

Html2wp Codex Plugin — Development skill for Claude Code

Development community

Convert HTML to WordPress.

How to install Html2wp Codex Plugin

This entry records only its repository, not the path inside it, so there is no exact command to give. Open iOSDevSK/html2wp-codex-plugin and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Html2wp Codex Plugin does

Convert HTML to WordPress. A Codex plugin that turns a static HTML site — Lovable, Bolt, v0, Claude artifacts, hand-written pages — into a real WordPress block theme: pixel-identical, editable, no page builder, WooCommerce for shops.

Alternatives in Development

Screenshot — Capture desktop, app windows, or pixel regions across OS platforms 14.6k ★
JWT Scan — JWT attack toolkit (offline) — alg:none forgery, RS256→HS256 algorithm confusion, weak-secret crack, static cl 4.5k ★
Fidelity — Measure how faithfully a clone reproduces a site — pixel-diff plus motion-fidelity into one 0-100 score, a let 3.6k ★

README

html2wp — convert HTML to a WordPress theme

**HTML to WordPress — pixel-identical, and still editable.**

A Claude Code and Codex plugin that converts HTML to WordPress: a static site, or anything that builds to one (Lovable, Bolt, v0, Claude artifacts, Next.js export, hand-written pages), becomes a standalone WordPress block theme. Pages, blog, forms, menus, SEO and redirects work with **no plugin required**. The markup stays the design's own — no page builder, no rebuild.

**Beta.** This converts real sites and is used on real work, but the gates catch most fidelity drift, not all of it. The last stage of every conversion is your own page-by-page review, and the skill walks you through it. Do not promise a client a result you have not looked at.

**Full documentation: [html2wp.dev/docs](https://html2wp.dev/docs)**

How it works

Your machine does the browser work — prerendering, screenshot and structural comparison, and a throwaway WordPress in Docker for the final checks. The html2wp service generates the theme: your **built site is uploaded to it**, because that is what the conversion is performed on, and the theme comes back. (Exactly which files travel is listed in `SKILL.md` under *What goes up*; stage 1 keeps credential-shaped files such as `.env` out of that payload and names every one it dropped.) What comes back is yours: readable PHP, CSS and JS, no lock-in, and a theme that calls nothing at runtime — the delivered site talks to no server of ours, ever.

Every stage ends in a **gate**, and a failed gate stops the pipeline. The conversion is compared against the original at three viewport widths, and the result is installed into a real WordPress and driven before it is handed over.

What the skill reports back

This section is about the **verdicts**, which travel separately from the upload above and long after it. Everything it says is scoped to that payload.

The gates run on your machine, against a WordPress the service never sees