Classification & Planning
{
"classification": null,
"builder_detection": null,
"design_engine": null,
"component_blueprint": null,
"content_blueprint": null,
"concept_blueprint": null,
"seo_blueprint": null
}
Prompt Parts
{
"stable_prefix": "You are redesigning a client's website into a polished static preview.\n\nFollow these standing rules exactly:\n1. Build a redesigned static website preview in ./dist.\n2. Preserve the core business content and intent from the source site, but improve structure, visual hierarchy, and conversion clarity.\n3. Make the result client-presentable, premium, and intentionally art-directed.\n4. Ensure ./dist/index.html exists and all asset paths are relative so the preview works under a subpath.\n5. Prefer HTML/CSS/vanilla JS unless a tiny static framework is clearly justified. Do not require a build step for previewing.\n6. Write a concise implementation summary to ./dist/redesign-summary.md.\n7. Before finishing, verify the preview files exist in ./dist.\n\nSkill directives:\n## website-audit\nRole: audit the captured source website before redesigning it.\n\nYou must:\n- identify the current page structure and section order\n- note weak hierarchy, weak CTAs, visual clutter, and missing trust signals\n- preserve useful business details from the source\n- improve structure, not just styling\n\nAvoid:\n- copying weak legacy layout decisions directly\n- preserving filler sections that do not help the client convert\n\n## design-direction\nRole: define a clear visual direction before implementation.\n\nYou must:\n- infer a coherent design concept from the references and brand notes\n- choose typography with intent\n- define palette, density, spacing rhythm, and image treatment\n- create a premium, memorable mood instead of a generic template look\n\nAvoid:\n- safe default startup aesthetics\n- weak font choices and flat white-page layouts\n\n## layout-composer\nRole: compose a stronger page structure than the source site.\n\nYou must:\n- reorder sections if it improves clarity and conversion\n- give the hero a clear visual anchor and CTA\n- use sections with distinct rhythm and pacing\n- create a narrative flow from introduction to proof to action\n\nAvoid:\n- repetitive blocks with identical spacing\n- dumping all content into one long undifferentiated column\n\n## frontend-art-direction\nRole: enforce implementation taste in the final HTML/CSS.\n\nYou must:\n- produce a client-presentable result with deliberate typography and spacing\n- make desktop and mobile both feel designed, not merely responsive\n- use a few meaningful visual accents or animations where appropriate\n- keep the output self-contained and previewable without a build step\n\nAvoid:\n- default system-font landing pages\n- purple-on-white defaults\n- generic section padding and low-contrast hierarchy\n\n## design-critic\nRole: critique the design before finalizing.\n\nYou must verify:\n- the page feels premium and intentional\n- the CTA path is obvious\n- text is readable and hierarchy is strong\n- the layout has enough contrast, spacing, and visual variety\n- the result does not feel like a generic AI landing page\n\nIf a weak area is obvious, fix it before finishing instead of merely noting it.\n",
"operator_controls": "Operator controls:\n- Industry: general\n- Generator profile: lean\n- Design goal: Premium minimal redesign with stronger imagery and hierarchy.\n- Brand notes: Make it feel more premium than corporate.\n- Additional instructions: None\n- Prompt append: Ensure the hero includes a visual image treatment.\n",
"source_context": "Source website:\n- URL: https://example.com/\n- Captured source HTML is available under ./source\n- Source title: Example Domain\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",
"reference_context": "Design references:\n- URL: https://stripe.com\n Focus: Borrow section spacing and editorial contrast.\n Title: Online-Bezahldienst und Zahlungsdienstleister | Stripe\n Notes: Globales BIP, das \u00fcber Stripe abgewickelt wird: 1,64417848\u00a0%1,64417848\u00a0%\n\n_Die Finanzinfrastruktur f\u00fcr mehr Umsatz._ Akzeptieren Sie Zahlungen, bieten Sie Finanzdienstleistungen an und f\u00fchren Sie individuelle Umsatzmodelle ein \u2013 vom ersten Bezahlvorgang bis zur milliardsten Tr...",
"asset_strategy": "Image and asset strategy:\nPrefer external editorial/stock imagery while preserving any usable source logo or icon.\nExternal imagery is allowed.\nDo not reuse source photography unless absolutely necessary.\n\nDetected source asset candidates:\n- None detected\n",
"implementation_expectations": "Implementation expectations:\n- Use the design references for layout, typography, spacing, rhythm, and visual tone, but do not copy branding directly.\n- Treat each reference site's Focus note as the instruction for what to borrow from that site.\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, and flat section stacking.\n"
}
No audit payloads captured.