Rebuild a page pixel-for-pixel
Capture a real page, build a static mirror and a live version, then repair the weakest fidelity signals until they match.
Use this when
Use War Loops when an authorized interface must be rebuilt from a URL or image and judged on appearance, motion, and responsive behavior.
How it runs
- Capture the source with a genuine browser and extract its design spec, motion, and target viewports.
- Build the static Pencil mirror and moving Forge version from the verified spec.
- Judge both across static design, experiential motion, and responsive reflow.
- Repair the weakest signals without rebuilding what already matches, then repeat to a terminal fidelity decision.
Done when
✓ The builds match the source across all three fidelity axes. Static appearance, experiential motion, and responsive reflow pass their gates, or the run reports stagnation or a blocked capture.
Why it works
War Loops separates a page's still appearance from how it moves and reflows. Its surgical critic targets the weakest measured signals without churning areas that already match.
Implementation note
The source implementation uses War Loops with Pencil and Forge. Confirm authorization to reproduce the reference, and stop on a bot wall, login gate, or unreliable capture.
More design loops
Build React UI to spec
Construct React components and UI elements, checking Thread #10 for completion criteria and exit signals.
Build frontend UI to signal
Iteratively build frontend UI components while polling oracle threads for an EXIT LOOP signal, up to 50 iterations.
Delete dead CSS, pixel-safe
Remove one unused or redundant style at a time and keep it gone only when every tested screen looks identical.