To rebuild an entire page, I wrote a Claude skill that chains six steps: research, page template, dedicated form, visuals, publishing and checks. With it, seven thematic pages on my site went from the old version to the new one in two days, each step approved by me before being published.
The principle of a skill is familiar: a written procedure the agent follows every time. This one is the longest I have written, because a rebuilt page isn’t just text.
The template: ten blocks and a header
All the pages follow the same plan, which lets me produce them in series:
- “The limits of your current tool”: three cards, “common limit of tools on the market, my solution’s answer”. The reader already has a tool, so we don’t explain what the product is.
- Three “text and visual” blocks, alternating light, dark, light: a title, a line saying where to find the feature in the interface, three or four factual bullets, and a figure as proof.
- Figures from case studies, with the case’s name in the label and the source.
- Three cases to read.
- A bridge to the next page in the journey.
- “Go further”: guide, article, support.
- The form, with an anchor so that every button leads to it.
- An FAQ of five questions.
The skill’s six steps
1. Research, before writing. Read the current page; query Search Console on the page’s queries and the topic’s queries across the whole site, so as not to cannibalize a guide that already carries the query (we then link to it); keep as a feature only what appears in the official documentation; take proofs from the table of customer results, with the exact figures; test every cited URL.
2. The template. The copy is written block by block following the plan above, with style rules (no long dash, the exact interface names) and SEO constraints: a title of 60 characters at most, a meta description of 155.
3. The dedicated form. A script creates the interest, duplicates a blank form and duplicates the internal alert for the new page. The fine wiring, in the tool’s builder, stays with me: I do it by hand rather than delegate it.
4. The visuals. Each visual is written in HTML then rendered to an image: one header and three visuals for the blocks. I look at each image and fix gaps and overlaps before showing a preview. Nothing goes live without my “go”.
5. Publishing. The media are uploaded with their alt text, title, caption and description. The page is written first as a dry run, then for real, with an automatic backup and a share image. Access goes through the mu-plugin described elsewhere.
6. The checks. Online, without cache: the title, the meta description, the images, the anchor and the buttons. Then a form audit script checks for each page: the right form, the right name, published, the alert, and the interests actually ticked in the public widget.
The safeguards
- No fact without a source: a feature that isn’t in the documentation isn’t claimed, and no quote is invented.
- Never an invented interface: a rebuilt card reuses the shape and values of a real screen, as in this rule.
- Preview and approval before any publication; dry run and backup before any write.
- A human for what commits: publishing the page, adding it to the menu, wiring the form.
What got in the way
- A figure pasted over a component is judged “crude”: if a value must change, the whole card is rebuilt.
- A repeated oversight on alerts: the alert copy kept the mention of the original page. Ten alerts were affected. The skill now passes the page address as a parameter.
- The skill ages: with each piece of feedback, I add the rule to the skill rather than to the conversation.
Key takeaway
A skill that covers the whole chain, from research to the online check, turns a rebuilt page into a repeatable procedure. The gain doesn’t come from writing speed, but from every step being written, checked, and no longer depending on my memory.