Workflows that ship

Overhaul an existing website without losing what works

Audit first, keep what earns its place, then rebuild page by page with the old site as a reference.

2 min read · prompt included

A redesign fails when it starts with the pretty part. A reliable order:

Inventory. Crawl the current site: every URL, its title, its purpose, its traffic if you have it. Ask the agent for a table.
Keep, merge, kill. For each page decide. Pages that rank or convert stay (and keep their URLs); thin pages merge; dead pages redirect.
Find the real problem. One sentence: "visitors reach pricing and leave", "mobile is unusable". Design for that sentence.
Direction before pixels. Write a one-page brief: audience, tone, three adjectives, two reference sites, tokens (colours, type, radius).
Rebuild the home page first at 390px, then desktop. Review. Then every other page reuses the same blocks.
Redirect map and checks. 301s for changed URLs, metadata, sitemap, a Lighthouse pass, then launch.

Never delete the old site until the redirect map is verified.

Prompt · Website overhaul

We are overhauling [site URL]. Work in this order and stop after each step for my approval.
1. Crawl the site and produce a table: URL, page title, purpose, what it should do for the visitor, keep / merge / kill with a reason.
2. Summarise the single biggest problem in one sentence and the evidence.
3. Write a design brief: audience, tone in three adjectives, two reference sites and what to take from each, and a token sheet (colours, fonts, radius, spacing, motion).
4. Propose the new sitemap and the section order for the home page, using blocks from the VibeBox Motion library where they fit.
5. Only then rebuild the home page, mobile first. Keep URLs that rank; list every redirect in docs/redirects.md.
Never invent reviews, numbers or logos; show fill-ins for missing facts.