website-redesign

Extract the full source first: dump the landing page with a real browser, walk every route and detail page, and parse embedded Next.js data payloads. Build a field and feature checklist, then restyle against it and report carry-over explicitly.

Load the target brand's template with exact colors, typography, and components, then apply those tokens to the app's existing composition. Keep the Monitor surface type, use monochrome plus one accent, and avoid marketing heroes on dashboards.

Yes, the output framework must match the source. If the input is a TSX/JSX or Next.js codebase, scaffold the same stack (Vite, React, Tailwind, shadcn) and restyle the existing surfaces rather than collapsing everything into one HTML file.

Read the source HTML and scripts statically to enumerate every element, route, and handler. Verify logic by executing the inline script under a mock DOM in Node, asserting row counts, filter results, and sort order without a visual render.

Agents typically rebuild only the visible landing screen and skip detail pages, modals, and tabs invisible on first paint. The fix is clicking through every route and parsing embedded data blobs before writing any CSS.

Drive a headless browser and probe the DOM: check row counts against parsed data, test filter clicks and drill-in behavior, and use CDP device metrics overrides for responsive tiers. Null-guard every getComputedStyle call to avoid aborted evaluations.