Website Builder Prompt v1.7.0
Updated for the admatic-staging-3 contract: Admatic Theme v1.14.2, central Core v2.14.1, Site Installer v5.13.1, Remote Worker v1.6.2 and Kit Factory v2.13.1.

Create an Admatic Kit Factory project package for this website.

The reference-first builder is the architecture authority. Before writing copy, compile an admatic.site-plan.v2 provisional envelope from the brief, profiles and page recipes. Analyse the references before choosing components. Core computes the canonical SHA-256 fingerprint only after the resolved page, global-part, media and composition contracts are committed.

The provisional envelope must include templateStructureContract. Use the selected Cavanio/service, fitness/performance, Nivaya/wellness, Ristera/hospitality or balanced corpus family to complete unseen page regions, section depth, header/footer topology and responsive reflow. Direct screenshot evidence and explicit blueprint rules always win. Never flatten the family into a generic four-section site, and never copy template-kit branding, copy, images or addon widgets.

Do not ask the content model to choose layout. Do not ask the package stage to reinterpret the brief. Content may fill only the variables declared by the selected component variant. Package generation must instantiate the locked approved variants. Repair may alter variables, media and global tokens first; a structural change requires a newly compiled fingerprint and approval.

Extract reference geometry before plan lock. Use approved-library sections and global parts only when measured structural similarity meets the fidelity threshold. Otherwise use a budgeted admatic.native-composition.v2 tree with explicit mismatch evidence. Raw Elementor JSON and arbitrary widget trees remain forbidden.

All new projects use the Admatic Elementor Pro Production Standard. Elementor Pro is a hard dependency, not an optional enhancement. The finished site must include published Elementor Pro Theme Builder global header and footer templates, both assigned to Entire Site, and every page must preserve them with the Elementor Full Width/header-footer layout.

The final website must be built directly through our confirmed Admatic workflow:
1. Admatic Core v2.8.0+ on dev-admatic.dk as the only MCP, OAuth and ChatGPT control plane; never install or require Core on staging
2. Site Installer v5.13.1+ on staging to install and synchronize the local stack
3. Remote Worker v1.6.2+ on staging for the protected Core handoff
4. Kit Factory v2.13.1+ and Admatic Theme v1.14.2+ on staging for import and Elementor execution
5. Finish by calling admatic/sites/build-project once, without dryRun, so Core compiles the ZIP and staging imports and starts the protected build automatically
6. Retain the returned public workflow ID and poll admatic/workflows/get-status until data.releaseGate.releaseReady is true; if that tool is unavailable, read data.releaseGate from admatic/projects/get-summary or admatic/qa/run-package-validation
7. Do not make native Elementor Website Kit export part of the default flow
8. Include an optional Kit Factory template/package export option only for moving the built
package to another site later
9. Do not manually assemble the final main Elementor Website Kit ZIP and never call a staging Worker REST endpoint directly

Your task:
Create the complete locked Core draft, then call admatic/sites/build-project once. Core owns ZIP compilation and signed delivery; do not stop to ask for approval keys or ask the user to move the automatic package manually.

The returned Core artifact URL is the manual fallback. Do not create a native Elementor Website Kit ZIP.

Important:
The Admatic Kit Factory project package ZIP is the main deliverable.
The website should be ready after Kit Factory Build.
Do not create or rely on a manually assembled native Elementor Website Kit ZIP.
Native Elementor export is not part of the default flow.

==================================================
PROJECT BRIEF SOURCE OF TRUTH
==================================================

Use the PROJECT BRIEF section inserted by Admatic Kit Factory Prompt Manager above these modules as the only source of truth for client/project information.
Do not add or repeat placeholder project info fields.

Visual reference:
Use the uploaded screenshots/images as the visual reference.
Treat reference_asset_urls as evidence attachments only. Treat media_asset_urls as production-media intake. When logo_attachment_id/logo_asset_url is supplied, use the public logo_asset_url as the Core download source, preserve logo_attachment_id as the originating staging Media Library identity, and bind the resulting assetRole=brand-logo item to the global header logo control. Do not treat a staging attachment ID as a Core attachment ID without explicit Core resolution.


The generated PROJECT BRIEF may contain a SITE DESIGN BLUEPRINT. Treat that blueprint as the project-specific design contract:
- explicit blueprint rules override uncertain visual inference
- directly visible screenshot evidence overrides generic fallback patterns
- rules marked as must keep or must avoid are mandatory
- do not silently replace project-specific rules with a familiar template
- preserve the blueprint inside project.json as design_blueprint so it remains available for later validation, export and repair

Accessible design setup:
- Automatic from reference is the default and recommended mode. The general user is not expected to know container widths, grid behavior, typography scales or section rhythm.
- In automatic mode, analyse the uploaded reference and create a complete internal Site Design Blueprint before generating Elementor content.
- In guided mode, use the selected preset and simple style controls for areas not shown.
- In advanced mode, explicit manual rules override automatic analysis.
- Blank advanced fields never justify a generic or under-specified website.

Clean build requirement:
- Add "build_policy": { "clean_previous_build": true } to project.json.
- A new build must replace Kit Factory's own previous pages, templates, reusable sections, menus, imported media and frontend QA files instead of accumulating old build content.
- Never delete unrelated manually created WordPress content.

Production standard requirement:
- Set strict_validation to true.
- Add project_standard.id = "admatic-elementor-pro-production" and project_standard.revision = "2026-07-16-modern-v5-1".
- Declare required Elementor and Elementor Pro dependencies exactly as defined by the shared standard JSON.
- Set page_layout_default and every page template to "elementor_header_footer". Elementor Canvas is forbidden.
- Create populated global-header and global-footer Theme Builder templates using a structurally matched approved component or bounded native Elementor composition.
- Store component/component_version on each global template and mirror the same ID/version into the first root Elementor container as admatic_component_id/admatic_component_version.
- Give both templates exact conditions ["include/general"] and display_conditions ["entire_site"].
- Use Elementor Pro Nav Menu widgets in both global templates and connect primary/footer WordPress menus.
- Preserve the required admatic-global-header and admatic-global-footer frontend markers.
- Use Header V2 with nested brand, navigation and action zones inside a measured content width. Keep it on one non-wrapping row with justify_content: "space-between" and align_items: "center". Use a real assetRole: "brand-logo" image or native text wordmark, bound its maximum width/height, enable the Nav Menu Full Width control and hide the CTA on mobile.
- Put admatic-header-brand directly on the Image, Site Logo or Heading wordmark widget, admatic-header-menu directly on the Nav Menu widget and admatic-header-cta directly on each desktop CTA Button widget. Never put these role markers on surrounding containers. Give the brand/menu widgets auto mobile width and set hide_mobile: "yes" on every header CTA button. The opened mobile menu may flow below the row; the closed header must never stack.
- Include referenceGeometry and visualCorrectionContract plus canonical frontend_screenshot_qa metadata for three viewports per page. Kit Factory captures them automatically, performs region-weighted comparison or structural benchmark fallback, maps failed regions to native controls and rerenders the same project without losing media or identity.

Match the layout, spacing, card style, colors, typography direction, header style, hero style,
section rhythm, background treatment, image placement, CTA style and overall visual feeling
as closely as possible.

The final website should feel close to 1:1 with the reference design direction, but adapted to
the client's brand, content and conversion goal.

Do not reuse a fixed template.
Do not create a plain/simple layout that only loosely follows the reference.
Do not only copy the colors; the structure, section rhythm, card styling, spacing, image
treatment and visual hierarchy must also follow the reference.

Build a fresh custom Elementor/Admatic Kit Factory project based on the provided
screenshots and project info.

Important image rule:
Do not screenshot, crop, trace, recreate, redraw, generate from, or reuse uploaded visual
reference images as placeholder assets.
Use uploaded screenshots only as visual/layout/style references.


When client images are missing, use only real photographic Unsplash placeholder images or
other approved real photo sources.
Do not generate, draw, synthesize, create abstract placeholder images, or create AI-style
local graphics.
Do not create decorative/generated placeholder images based on the visual reference.
All placeholder images must look like real photography and be relevant to the business type.

ADMATIC REFERENCE-FIRST RELEASE GATE V4 — MANDATORY
- A reference-led project cannot pass from schema validation, capture success, baseline creation or structural heuristics alone.
- comparison.available=false, comparisons=0, baselineCreated-only, structural-advisory or missing viewport mapping must set releaseReady=false.
- Structural analysis is advisory and may identify corrective controls, but it may never contribute synthetic perfect region scores or satisfy rendered reference comparison.
- Header, hero, sections, typography, imagery and footer each have independent minimum thresholds. A failed critical region triggers same-project correction even when the weighted average passes.
- Approved components require measured structuralMatch.score >= 0.96 plus evidence. Otherwise use admatic.native-composition.v2. Never silently substitute utility-message, global-header/classic or global-footer/columns in a reference-led plan.
- The header brand Image control may bind only to an assetRole=brand-logo manifest entry. With no valid brand logo, render a native text wordmark. Any content-photo in the brand control is a blocking validation failure.
- Prefer explicit Elementor Grid containers for repeated structures. Flexbox wrap is forbidden for card, feature, service, testimonial, price and gallery collections.
- Supported global-part families include overlay navigation, centered-logo split, utility-bar + primary, editorial asymmetric, contact-heavy footer, editorial wide footer, compact legal footer and CTA-led footer. Select by measured geometry, not industry defaults.



MODERN GOLDEN STANDARD V4 — CREATIVE EXPRESSION CONTRACT
- Visible reference evidence is authoritative. Reconstruct its section sequence, geometry, media rhythm, visual density, hierarchy, surface changes and conversion flow before selecting components.
- Do not default to repeated bare heading/text card grids. A standard homepage should normally contain 10–14 distinct visual regions; inner pages should normally contain 6–10.
- Approved components are optional candidates, not mandatory output. Use them only at measured structural match >= 0.96. Otherwise use expressive admatic.native-composition.v2 structures.
- Creative freedom is open inside native Elementor controls. Use Grid, nested containers, images, galleries, counters, icons, icon lists, testimonials, forms, accordions, tabs, carousels, dividers, backgrounds, overlays, borders, radii, soft shadows, typography and responsive controls.
- Hard restrictions only: direct Position remains Default; no custom CSS; no HTML widgets; no flex wrap; no arbitrary tracking/design classes. Multi-column layouts use native Elementor Grid with explicit desktop/tablet/mobile columns.
- Modern surface language: subtle 1px borders, 12–32px radii, soft low-opacity shadows, alternating dark/light or accent/quiet regions, deliberate image crops and clear content max-widths. Avoid every section looking like the same flat dark rectangle.
- Mobile must satisfy document.scrollWidth <= document.documentElement.clientWidth + 1 at 390px. Clear fixed/oversized widths, negative margins and multi-column mobile grids; mobile grids collapse to one column.
- Use at least four media-led regions on a standard homepage when enough media is available. Prefer editorial split layouts, image mosaics, location cards, quote/proof panels and richer CTA/footer transitions.

V5 PLANNING RULE
Treat the licensed corpus as a pattern grammar. Use editorial splits, image mosaics, framed media panels, layered bands, native Grid, mixed open/card layouts, carousels, location systems, pricing comparisons, loops, timelines and immersive heroes only when they match the measured reference and content purpose. Never select the nearest generic component merely because it exists.

TEMPLATE INVENTORY AND SCREENSHOT-AUTHORITY POLICY
- Keep curated components for headers, footers, menus, forms, navigation and other high-risk global structures. Component count is never a quality target.
- Treat every approved template inventory entry as searchable geometry, responsive, widget and surface-treatment knowledge—not as a rigid layout to clone. The inventory is designed for 50–100+ curated full-site templates and hundreds of classified section patterns.
- The supplied screenshot reference is always the primary authority. Analyse it before retrieval, measure its geometry, and never let an industry label or nearest template override visible evidence.
- Retrieve multiple candidates: up to five whole-page shells and up to eight candidates per region. Use a whole template only when measured whole-page geometry and section topology strongly match; otherwise synthesize regions from multiple corpus patterns.
- Use native Elementor composition for most screenshot-specific page regions. Allow all installed first-party Elementor and Elementor Pro widgets except HTML and other explicitly prohibited controls.
- Score corpus candidates by geometry 30%, section topology 20%, responsive behaviour 15%, image composition 10%, typography hierarchy 10%, surface styling 10%, and widget compatibility 5%. Industry similarity is secondary.
- Reconstruct patterns with native Elementor controls. Never copy source branding, text, photography, licence data or third-party addon dependencies.
- Render desktop, tablet and mobile, compare against the supplied reference, and correct the same project up to three evidenced passes. Do not create a duplicate project.
