{
  "stable_prefix": "You are redesigning a client's website into a polished static preview.\n\nRules:\n- Build the redesigned static preview in ./dist.\n- Preserve business facts and intent from the source while improving hierarchy, clarity, and conversion.\n- Keep the result premium, art-directed, and previewable without a build step.\n- Ensure ./dist/index.html exists and all asset paths are relative.\n- Write a concise ./dist/redesign-summary.md before finishing.\n\nWorking directives:\n- Audit the source site, preserve useful facts, and improve weak hierarchy or CTA paths.\n- Establish one clear art direction before building; typography, palette, rhythm, and imagery should feel intentional.\n- Recompose the page for narrative flow instead of preserving legacy ordering blindly.\n- Deliver polished static HTML/CSS/JS in ./dist with strong mobile behavior and obvious conversion paths.\n- Self-critique before finishing and fix any obvious generic, low-contrast, or weak-hierarchy issues.\n- Active skill packs: website-audit, design-direction, layout-composer, frontend-art-direction, design-critic.\n",
  "design_guardrails": "Pre-generation design guardrails:\n- Do not use overused default fonts like Inter, Roboto, Open Sans, Lato, Montserrat, or Arial as the primary personality font unless the selected design family explicitly calls for them.\n- Do not use gradient text, decorative background-clip text, or flashy AI-tell effects.\n- Ensure body text and CTA text clearly exceed WCAG AA contrast; do not leave near-failing warm-on-cream combinations.\n- Do not animate layout properties like width, height, padding, or margin. Prefer transform and opacity.\n- Avoid uppercase for long body copy; reserve it for short labels only.\n- Avoid generic SaaS hero composition, default Tailwind landing-page stacking, and interchangeable startup polish.\n- Build the first draft from the internal design family and concept blueprint. Do not rely on copied public-site patterns.\n- Always include a real location module near the footer with address, hours, phone, and a real map/embed or directions link.\n- Do not use old-site navigation links such as legacy menu/about/contact URLs in the redesigned preview.\n- Do not fabricate testimonials, review attributions, awards, ratings, or statistics that are not present in the extracted source facts or enrichment.\n- Rewrite source marketing copy; do not copy long source paragraphs verbatim into the redesign.\n",
  "operator_controls": "Operator controls:\n- Run mode: refined\n- Industry: general\n- Design family: warm-hospitality\n- Generator profile: balanced\n- Source expansion mode: balanced\n- Search enrichment: True\n- Search budget: 4\n- Content audit: critique=True, autofix=True\n- SEO audit: critique=True, autofix=True\n- Lighthouse audit: critique=True, autofix=False\n- Axe audit: critique=True, autofix=False\n- Impeccable audit: critique=True, autofix=True\n- Design goal: General premium redesign\n- Brand notes: None\n- Additional instructions: None\n- Prompt append: None\n",
  "business_profile": "Business profile:\n- Business name: Princess Maria Diner\n- Category: general\n- Address: 2044 Rte 35 North, Wall NJ 07719\n- Phone: 732-282-1722\n- Hours: 7:00am - 10:00pm\n- Maps link: https://www.google.com/maps/search/?api=1&query=2044+Rte+35+North%2C+Wall+NJ+07719\n- Core highlights:\n  - family-owned\n  - over 30 years\n  - breakfast\n  - lunch\n  - dinner\n  - exceptional service\n",
  "seo_requirements": "SEO requirements:\n- Canonical URL: https://princessmariadiner.com/\n- Schema type: LocalBusiness\n- Title formula: Princess Maria Diner | General in Wall NJ 07719\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: family-owned, over 30 years, breakfast, lunch\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- Business 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  - family-owned\n  - over 30 years\n  - breakfast\n  - lunch\n  - dinner\n  - exceptional service\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://princessmariadiner.com/menu\n  - https://princessmariadiner.com/\n",
  "source_context": "Source website context:\n- URL: https://princessmariadiner.com/\n- Captured source HTML is available under ./source\n- Source title: Princess Maria Diner - Restaurant in Wall, NJ\n- Completeness score: 1.00\n- Completeness notes:\n  - source markdown has usable length\n  - metadata description found\n  - important internal links discovered\n  - logo-like asset found\n  - multiple visual assets found\n  - business facts present in extracted content\n- Source summary:\n2044 Rte 35 North, Wall NJ 07719\n\n[732-282-1722](tel:7322821722)\n\nOpening Hours : 7:00am - 10:00pm\n\n[](https://x.com/Mariadiner)\n[](https://www.facebook.com/Princess-Maria-Diner-115652971791226/)\n\n[![Princess Maria Diner](https://princessmariadiner.com/assets/logo-418779bfc65e80a126fe5aaad4864e1b6a9e9f5369431ad16d2a56cf3e745230.png)](h...\n- Important discovered links:\n  - https://princessmariadiner.com\n  - https://princessmariadiner.com/menu\n  - https://princessmariadiner.com/gallery\n  - https://princessmariadiner.com/contact\n- Source asset strength: strong\n",
  "design_family": "Internal design family:\n- Family: warm-hospitality\n- Selection source: inferred\n- Rationale: default for industry=general; language suggests warm hospitality positioning\n- Summary: Tactile, welcoming, and polished neighborhood-premium direction for food, beverage, and service brands.\n- Typography direction: Soft serif or humanist display with warm sans-serif support.\n- Palette logic: Stone, parchment, terracotta, deep espresso, and muted olive accents.\n- Layout direction: Story-led hero, cozy content width, layered imagery, and rhythm built around atmosphere and trust.\n- Component language: Rounded CTA pills, proof strips, gallery clusters, and service cards with subtle warmth.\n- Motion rule: Minimal parallax feel through composition only; motion stays subtle.\n- Family anti-patterns: Avoid harsh black-on-white tech aesthetics and sterile card walls.\n",
  "component_blueprint": "MagicUI-inspired component blueprint:\n- Source: magicui-inspired internal component vocabulary\n- Business subtype: general\n- Hero pattern: welcoming split or layered hero with food-led photography, short appetite-first headline, and immediate visit/order CTA\n- Nav pattern: friendly compact nav with rounded CTA and clear menu/location anchors\n- CTA pattern: rounded warm CTA buttons with strong text contrast and obvious tap targets\n- Surface pattern: soft elevated cards, warm background bands, and cozy content containers with visible breathing room\n- Gallery pattern: collage-style gallery clusters with varied image sizes and appetite-first crops\n- Proof pattern: trust strip, family story block, and short review-style proof only when evidence exists\n- Menu / offering pattern: visual menu highlight modules organized by breakfast/lunch/dinner or signature specialties, built into the page\n- Footer pattern: high-trust footer with address, phone, hours, map embed or directions link, and quick visit CTA\n- Motion pattern: gentle reveal and hover polish only; no distracting scene changes\n- Decorative pattern: warm chips, badges, dividers, and subtle grain/texture cues without fake retro clutter\n- Family-specific adaptations:\n  - None\n",
  "concept_blueprint": "Concept blueprint:\n- Creative thesis: Tactile, welcoming, and polished neighborhood-premium direction for food, beverage, and service brands.\n- Typography system: Soft serif or humanist display with warm sans-serif support.\n- Color logic: Stone, parchment, terracotta, deep espresso, and muted olive accents.\n- Layout system: Story-led hero, cozy content width, layered imagery, and rhythm built around atmosphere and trust.\n- Component language: Rounded CTA pills, proof strips, gallery clusters, and service cards with subtle warmth.\n- Conversion priorities: primary-cta, trust, clarity\n- Content focus: family-owned, over 30 years, breakfast, lunch, dinner\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- None used (source content considered sufficient)",
  "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- https://princessmariadiner.com/assets/logo-418779bfc65e80a126fe5aaad4864e1b6a9e9f5369431ad16d2a56cf3e745230.png (logo)\n- https://princessmariadiner.com/cdn/rs3ha06vhp7te2p5sjnr2es9ua1d/pork-roll-egg-cheese-bkgd.jpg (general)\n- https://princessmariadiner.com/assets/gallery/coffee-bar-at-work-58aa315144eff144fad230833006e90bc61ea18ff0b451b5d7cf83ade7400bbf.jpg (general)\n- https://princessmariadiner.com/assets/gallery/coffee-bar-close-up-view-d66c956fc6ac1fbc7ced300098a2b4174e7f1523530ab1289262a74959c97a3c.jpg (general)\n",
  "implementation_expectations": "Implementation expectations:\n- Use the internal design family and concept blueprint as the dominant visual system.\n- The source website is for business facts, proof, usable assets, and service/menu details, not for visual inspiration.\n- Do not imitate or scrape public reference websites. Create a bespoke concept from the internal design family.\n- Re-express the source business in the selected family\u2019s typography, spacing, component language, and section rhythm.\n- Treat the MagicUI-inspired component blueprint as concrete UI direction for the first pass, not optional inspiration.\n- The first draft should already feel art-directed and prospect-ready, not like a template adaptation.\n- The first draft must also be SEO-ready: title, description, canonical, OG/Twitter metadata, one clear H1, and valid LocalBusiness-style JSON-LD should already be present.\n- Include a real map or directions embed/link in the closing/footer area using the actual business location. Do not replace the location module with decorative imagery.\n- Do not send users back to the old website for key content. Rebuild critical content like menus, services, FAQs, and offers directly inside the redesign.\n- If trustworthy review copy or ratings are not available in the extracted source context, omit testimonial quotes rather than inventing them.\n- Rewrite key content according to the rewrite targets and required sections instead of restyling the source page one section at a time.\n- 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.\n- If external images are allowed, you may use tasteful editorial/stock imagery that fits the brand and note that choice in redesign-summary.md.\n- If the captured content is incomplete, infer sensible placeholders while keeping the preview coherent.\n- Avoid generic AI landing-page patterns, default fonts, flat section stacking, and startup-style feature grids.\n"
}