clone-website
Clone Website Skill
Reverse-engineer any website into production-ready Astro 6 code using agent-browser for headless scraping. Extraction and construction happen in parallel — as each section is inspected, a detailed spec is written and handed to a builder agent working in an isolated git worktree.
Guiding Principles
- Completeness Beats Speed — Every builder must have everything: screenshot, exact CSS values, downloaded assets with local paths, real text, component structure. Extract the extra property rather than ship an incomplete brief.
- Small Tasks, Perfect Results — Single-component sections get one builder agent; multi-variant sections get one agent per variant. If a builder prompt exceeds ~150 lines of spec, split the section.
- Real Content, Real Assets — Extract actual text via
element.textContent, download every<img>and<video>, convert inline<svg>to components. Check for layered compositions (background + foreground + overlay). - Foundation First — Global CSS tokens, fonts, TypeScript types, and global assets must exist before any section building. Sequential, non-negotiable. Everything after is parallel.
- Extract How It Looks AND How It Behaves — Document appearance (exact computed CSS via
getComputedStyle()) AND behavior (what changes, trigger, transition). Not "looks liketext-lg" but the actual computed value. - Identify Interaction Model Before Building — Answer definitively: Is this click-driven, scroll-driven, hover-driven, time-driven, or mixed? Scroll first before clicking. If things change as you scroll, extract the mechanism. If not, then click/hover test. This is the #1 most expensive mistake — wrong interaction model requires a complete rewrite.
- Extract Every State, Not Just Default — Click each tab/button, extract content per state. For scroll-dependent elements: capture computed styles at position 0, scroll past trigger, capture again, diff them.
- Spec Files Are Source of Truth — Every component gets a spec file BEFORE dispatch. The spec is the contract between extraction and builder. Non-optional.
- Build Must Always Compile — Every builder verifies the build passes before finishing. Broken build is never acceptable, even temporarily.
Prerequisites
Before starting, verify tools are installed:
More from pengelbrecht/skills
agent-screencast
>
6missions
>
3gws-slides
>
3claude-code-tutor
>
2lore
Connect to a Lore backend — query data, mutate with governance, propose schema changes, contribute knowledge. Use when an agent needs to interact with a Lore instance for reading/writing data, proposing DDL, or learning. Triggers on "connect to lore", "query lore", "lore schema", "propose table", or any task involving a Lore API.
1metricly-author
Conventions for writing dbt YAML descriptions and the org's business_context doc. Use when editing dbt/models/**.yml, dbt/context/business_context.md, or any file that feeds Metricly's semantic layer or org context.
1