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