{
  "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- For restaurants, prioritize appetite appeal, atmosphere, reservations, hours, location confidence, and concise menu highlights.\n- Active skill packs: website-audit, design-direction, layout-composer, frontend-art-direction, design-critic, restaurant.\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: restaurant\n- Design family: warm-hospitality\n- Generator profile: lean\n- Source expansion mode: strict\n- Search enrichment: True (budget=2)\n- Design goal: General premium redesign\n- Brand notes: None\n- Additional instructions: None\n",
  "business_profile": "Business profile:\n- Business name: Princess Maria Diner\n- Category: restaurant\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: Restaurant\n- Title formula: Princess Maria Diner | Restaurant 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- Subtype: restaurant-diner\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: Do not link out to the legacy menu page. Rebuild menu highlights, featured dishes, pricing cues, and dayparts as part of the redesigned experience.\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  - family story / trust strip\n  - breakfast-lunch-dinner menu highlights\n  - signature dishes or comfort-food feature band\n  - photo-led atmosphere / gallery\n  - visit info with hours, phone, address, and map\n- Rewrite targets:\n  - hero copy\n  - value proposition\n  - CTA copy\n  - menu highlights\n  - about copy\n  - visit/location copy\n- Section notes:\n  - Reframe the business as a beloved, reliable local diner rather than a generic restaurant.\n  - Preserve diner warmth and familiarity while making the menu presentation more polished and persuasive.\n  - Prefer rewritten section copy with stronger appetite appeal over literal source reuse.\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- Detected industry: restaurant (confidence=1.00, source=inferred)\n- Detection signals: dinner, lunch, breakfast, diner, menu, restaurant, eat, menu url\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/asse...\n- Important discovered links:\n  - https://princessmariadiner.com\n  - https://princessmariadiner.com/menu\n  - https://princessmariadiner.com/gallery\n- Source asset strength: strong\n",
  "design_family": "Internal design family:\n- Family: warm-hospitality\n- Selection source: inferred\n- Rationale: default for industry=restaurant; niche subtype restaurant-diner maps best to warm-hospitality\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: restaurant-diner\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  - Favor honest appetite-led photography over moody luxury staging.\n  - Keep menu highlights immediately scannable and daypart-driven.\n  - Use friendlier, neighborhood-scale typography and warmer surfaces.\n  - Prefer proof strips, service warmth, and visit confidence over aspirational brand theater.\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: call-now, location-and-hours, menu-confidence\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  - Warm hero with primary CTA\n  - Trust/story introduction\n  - Breakfast-lunch-dinner menu highlights\n  - Signature comfort-food band\n  - Photo-led atmosphere and visit close\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- 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"
}