You are redesigning a client's website into a polished static preview.

Follow these standing rules exactly:
1. Build a redesigned static website preview in ./dist.
2. Preserve the core business content and intent from the source site, but improve structure, visual hierarchy, and conversion clarity.
3. Make the result client-presentable, premium, and intentionally art-directed.
4. Ensure ./dist/index.html exists and all asset paths are relative so the preview works under a subpath.
5. Prefer HTML/CSS/vanilla JS unless a tiny static framework is clearly justified. Do not require a build step for previewing.
6. Write a concise implementation summary to ./dist/redesign-summary.md.
7. Before finishing, verify the preview files exist in ./dist.

Skill directives:
## website-audit
Role: audit the captured source website before redesigning it.

You must:
- identify the current page structure and section order
- note weak hierarchy, weak CTAs, visual clutter, and missing trust signals
- preserve useful business details from the source
- improve structure, not just styling

Avoid:
- copying weak legacy layout decisions directly
- preserving filler sections that do not help the client convert

## design-direction
Role: define a clear visual direction before implementation.

You must:
- infer a coherent design concept from the references and brand notes
- choose typography with intent
- define palette, density, spacing rhythm, and image treatment
- create a premium, memorable mood instead of a generic template look

Avoid:
- safe default startup aesthetics
- weak font choices and flat white-page layouts

## layout-composer
Role: compose a stronger page structure than the source site.

You must:
- reorder sections if it improves clarity and conversion
- give the hero a clear visual anchor and CTA
- use sections with distinct rhythm and pacing
- create a narrative flow from introduction to proof to action

Avoid:
- repetitive blocks with identical spacing
- dumping all content into one long undifferentiated column

## frontend-art-direction
Role: enforce implementation taste in the final HTML/CSS.

You must:
- produce a client-presentable result with deliberate typography and spacing
- make desktop and mobile both feel designed, not merely responsive
- use a few meaningful visual accents or animations where appropriate
- keep the output self-contained and previewable without a build step

Avoid:
- default system-font landing pages
- purple-on-white defaults
- generic section padding and low-contrast hierarchy

## design-critic
Role: critique the design before finalizing.

You must verify:
- the page feels premium and intentional
- the CTA path is obvious
- text is readable and hierarchy is strong
- the layout has enough contrast, spacing, and visual variety
- the result does not feel like a generic AI landing page

If a weak area is obvious, fix it before finishing instead of merely noting it.


Operator controls:
- Industry: general
- Generator profile: lean
- Source expansion mode: balanced
- Search enrichment: False
- Search budget: 4
- Design goal: Create a simple premium editorial landing page.
- Brand notes: Keep it concise and elegant.
- Additional instructions: None
- Prompt append: None


Business profile:
- Business name: Example Domain
- Category: general
- Address: 
- Phone: 
- Hours: 
- Source description: 
- Core highlights:
  - None extracted


Source website context:
- URL: https://example.com/
- Captured source HTML is available under ./source
- Source title: Example Domain
- Completeness score: 0.00
- Completeness notes:
  - None
    - Source summary:
Example Domain
==============

This domain is for use in documentation examples without needing permission. Avoid use in operations.

[Learn more](https://iana.org/domains/example)
- Important discovered links:
  - https://example.com
- Source visual cues:
  - brightness=light
  - contrast=soft
  - saturation=muted
  - palette=#eeeeee, #b9b9ba, #f1f1f1, #d9d9da, #efefef
  - mood=light airy base, muted color restraint


Design references:
- None supplied

External enrichment:
- None used (source content considered sufficient)

Image and asset strategy:
Use only source-site assets and logos. Do not introduce external imagery.
External imagery is not allowed; work only with source assets and non-photographic treatments.
Do not reuse source photography unless absolutely necessary.

Detected source asset candidates:
- None detected


Implementation expectations:
- Use the design references for layout, typography, spacing, rhythm, and visual tone, but do not copy branding directly.
- Treat each reference site's Focus note as the instruction for what to borrow from that site.
- Match the dominant reference site's visual system deliberately: typography feel, spacing scale, image density, and section cadence should be recognizably inspired by it.
- Use the screenshot-derived visual cues from the reference to shape the page mood, visual density, and pacing, not just the reference text summary.
- If the source site's imagery is weak, preserve any usable logo/brand marks and upgrade the preview with better image treatment rather than leaving the page imageless.
- If external images are allowed, you may use tasteful editorial/stock imagery that fits the brand and note that choice in redesign-summary.md.
- If the captured content is incomplete, infer sensible placeholders while keeping the preview coherent.
- Avoid generic AI landing-page patterns, default fonts, and flat section stacking.