{
  "stable_prefix": "You are redesigning a client's website into a polished static preview.\n\nCore rules:\n- Build in ./dist and ensure ./dist/index.html exists.\n- Keep all asset paths relative.\n- Preserve facts, but improve clarity, conversion, and presentation.\n- Keep the result premium, art-directed, and previewable without a build step.\n- Write a concise ./dist/redesign-summary.md before finishing.\n\nWorking directives:\n- Preserve facts, improve hierarchy, and strengthen conversion paths.\n- Pick one clear art direction before building.\n- Recompose the page instead of restyling the legacy layout.\n- Deliver polished static HTML/CSS/JS in ./dist with strong mobile behavior.\n- Fix obvious generic, low-contrast, or weak-hierarchy issues before finishing.\n- Active skill packs: website-audit, design-direction, layout-composer, frontend-art-direction, design-critic.\n",
  "design_guardrails": "Pre-generation design guardrails:\n- Avoid default-font personality, gradient text, and generic SaaS landing-page patterns.\n- Maintain strong body/CTA contrast and animate only transform/opacity.\n- Use the internal family, component blueprint, and concept blueprint as the primary design system.\n- Include a real location module near the footer with address, hours, phone, and a real map/embed or directions link.\n- Keep navigation internal to the preview; do not reuse legacy source-site URLs.\n- Do not fabricate testimonials, ratings, awards, or statistics.\n- Rewrite source marketing copy; do not lift long paragraphs verbatim.\n",
  "operator_controls": "Operator controls:\n- Run mode: prospect\n- Industry: general\n- Design family: modern-approachable\n- Generator profile: lean\n- Source expansion mode: strict\n- Search enrichment: True (budget=2)\n- Design goal: General premium redesign\n- Brand notes: Internal UI smoke test\n- Additional instructions: None\n",
  "business_profile": "Business profile:\n- Business name: Example Domain\n- Category: general\n- Address: \n- Phone: \n- Hours: \n- Maps link: \n- Core highlights:\n  - None extracted\n",
  "seo_requirements": "SEO requirements:\n- Canonical URL: https://example.com\n- Schema type: LocalBusiness\n- Title formula: Example Domain | General in your area\n- Meta description focus: Lead with the offer, atmosphere or trust angle, then reinforce location and a primary CTA in 120-160 characters.\n- Keywords to reinforce naturally: None\n- OG image strategy: Use the strongest hero or branded source image as the social preview image and ensure the meta tags point to it.\n- Heading rule: Use exactly one descriptive H1 and a logical H2/H3 hierarchy for major sections.\n- Alt text rule: Every non-decorative image should have descriptive alt text tied to the business, menu, service, or atmosphere.\n- Footer/location rule: Include a dedicated footer/location module with address, hours, phone, and a real Google Map embed whenever practical. At minimum, include a real directions link tied to the actual business location.\n",
  "content_integrity": "Content integrity requirements:\n- Subtype: general\n- Rewrite rule: Rewrite and improve source copy into sharper, clearer, more persuasive language. Preserve facts, but do not reuse long sentences verbatim.\n- Proof rule: Use only verifiable proof from source facts or extracted enrichment. If specific reviews, awards, or ratings are not present, do not invent them.\n- Link rule: Do not use legacy source-site navigation or CTA links in the redesigned preview. Keep navigation internal to the preview and rebuild important content as sections.\n- Menu rule: \n- Trust signals that may be emphasized:\n  - None extracted\n- Required sections:\n  - hero\n  - proof\n  - contact-footer\n- Rewrite targets:\n  - hero copy\n  - value proposition\n  - CTA copy\n- Section notes:\n  - None\n- Forbidden source URLs:\n  - https://example.com\n",
  "source_context": "Source website context:\n- URL: https://example.com\n- Captured source HTML is available under ./source\n- Source title: Example Domain\n- Detected industry: general (confidence=0.00, source=inferred)\n- Detection signals: None\n- Completeness score: 0.00\n- Completeness notes:\n  - None\n- Source summary:\nExample Domain\n==============\n\nThis domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n[Learn more](https://iana.org/domains/example)\n- Important discovered links:\n  - https://example.com\n- Source asset strength: weak\n",
  "design_family": "Internal design family:\n- Family: modern-approachable\n- Selection source: inferred\n- Rationale: default for industry=general\n- Summary: Fresh, airy, contemporary direction for small businesses that need clarity without feeling cold or templated.\n- Typography direction: Readable modern sans with one distinctive accent face or typographic treatment.\n- Palette logic: Clean light base, controlled accent color, and soft contrast surfaces.\n- Layout direction: Balanced hero, modular content rhythm, friendly proof sections, and sharp CTA moments.\n- Component language: Simple cards, image-text alternation, FAQ modules, and approachable callouts.\n- Motion rule: Light stagger and reveal only.\n- Family anti-patterns: Avoid flat default Tailwind landing-page layouts and interchangeable hero copy.\n",
  "component_blueprint": "MagicUI-inspired component blueprint:\n- Source: magicui-inspired internal component vocabulary\n- Business subtype: general\n- Hero pattern: balanced modern hero with approachable imagery, concise positioning, and clear primary CTA\n- Nav pattern: simple high-legibility nav with one strong CTA and tight section anchors\n- CTA pattern: clean rounded CTA with subtle depth and strong mobile sizing\n- Surface pattern: modular cards, clean background bands, and generous spacing\n- Gallery pattern: tidy alternating media blocks and modular image cards\n- Proof pattern: compact story/proof modules and clean FAQ sections\n- Menu / offering pattern: digestible highlight cards or mini-feature grids built into the main page\n- Footer pattern: clean footer with contact block, hours if relevant, and map/directions support\n- Motion pattern: light stagger and hover polish only\n- Decorative pattern: soft accent shapes and subtle dividers without trend-chasing visuals\n- Family-specific adaptations:\n  - None\n",
  "concept_blueprint": "Concept blueprint:\n- Creative thesis: Fresh, airy, contemporary direction for small businesses that need clarity without feeling cold or templated.\n- Typography system: Readable modern sans with one distinctive accent face or typographic treatment.\n- Color logic: Clean light base, controlled accent color, and soft contrast surfaces.\n- Layout system: Balanced hero, modular content rhythm, friendly proof sections, and sharp CTA moments.\n- Component language: Simple cards, image-text alternation, FAQ modules, and approachable callouts.\n- Conversion priorities: primary-cta, trust, clarity\n- Content focus: None\n- Footer requirement: Include a dedicated footer/location module with address, hours, phone, and a real Google Map embed whenever practical. At minimum, include a real directions link tied to the actual business location.\n- Section flow:\n  - Distinctive hero with clear CTA\n  - Value proposition and business story\n  - Services or featured offerings\n  - Proof / testimonials / imagery\n  - Conversion-focused closing section\n",
  "external_enrichment": "External enrichment:\n- example.com - Wikipedia\n  URL: https://en.wikipedia.org/wiki/Example.com\n  Notes: The domain names are used widely in books, tutorials, sample network configurations, an...\n- Example Domain\n  URL: http://www.example.com/\n  Notes: Example Domain is a domain name that can be used in documents without permission or coo...",
  "asset_strategy": "Image and asset strategy:\nUse a hybrid approach: preserve any usable logo or brand mark, reuse good source photos when credible, and supplement weak imagery with high-quality external/editorial imagery.\nExternal imagery is allowed.\nReusing source images is encouraged when quality is acceptable.\n\nDetected source asset candidates:\n- None detected\n",
  "implementation_expectations": "Implementation expectations:\n- Build from the internal design family, component blueprint, and concept blueprint.\n- Use the source for facts, proof, usable assets, and menu/service details, not for visual direction.\n- Rebuild key content inside the redesign instead of linking back to legacy pages.\n- Make the first draft prospect-ready: strong hero, clear CTA, persuasive rewritten copy, and real location info.\n- Include title, description, canonical, OG/Twitter tags, one clear H1, and valid LocalBusiness-style JSON-LD.\n- Use a real map or directions embed/link in the footer/location area; never replace it with decorative imagery.\n- If proof is weak, omit it rather than inventing it.\n- If imagery is weak, preserve usable brand assets and improve the image treatment without leaving the page visually empty.\n"
}