# Adapted prompt — lumora®

## 1. Source and intended fidelity

Read [the detailed source brief](../../11-LUMORA-DESIGN-ENGINEERING.md) and [the catalog entry](../../templates/44-lumora.md). Build an original, production-shaped static **design demonstration**, not an impersonation of an operating business. Preserve the visual narrative: **Considered design. Thoughtful engineering.**. Do not claim an exact recreation when the remote references have not been visually inspected.

## 2. Deliverables and architecture

Create semantic `index.html`, a site-specific `theme.css`, and use the collection's local shared modules. Keep the HTML content available before JavaScript. Store authoring data in `tools/catalog.py`; regenerate with `python3 tools/build.py`. Avoid React, Next.js, a server API, import-map CDNs, and runtime font requests. Three.js is pinned at 0.165.0 and served locally.

Use only relative local asset paths so the page runs both at `/getlayersai/sites/lumora/` locally and under `/WebsitedesignandPrompts/getlayersai/sites/lumora/` on Pages. A site is an independent address inside one project Pages deployment, not a new GitHub repository or domain.

## 3. Design language

Set background `#0d0e10`, text `#f2f1ed`, accent `#e8b668`, and panel `#1b1c1f`. Use the local font family appropriate to the authored design: Geist for the base UI, Syne for bold expressive headings, Cormorant for serif moments. Limit line lengths, preserve generous whitespace, and use clear mono labels for simulated technical readouts. Use the authored page's section order, copy, and unique layout from the `lumora` record in `catalog.py`, not a generic repeated landing-page shell.

## 4. Signature scene

A warm procedural Three.js caustic field sits behind a Swiss-grid hero. Asymmetric case-study cards use authored CSS artwork. Native disclosure rows cover capabilities; an Intl.DateTimeFormat clock renders Europe/Amsterdam without a network call.

Use a single animation scheduler with a delta capped at 32 ms. Pointer spring constants are tension 180 and friction 24; device pixel ratio is capped at 1.6. Render a still state when reduced motion is requested, pause offscreen and when the document is hidden, and retain a meaningful fallback if WebGL is unavailable. Direct interactions must remain usable without continuous motion.

## 5. Functional acceptance criteria

1. Open both case studies and each capability disclosure.
2. Verify Amsterdam clock renders without external requests.
3. Check asymmetric desktop layout collapses into a logical mobile order.

4. Every navigation link resolves to a real section or page. All primary inquiry actions open a labelled local modal, validate sample name/email, then clearly say that nothing was delivered or booked.
5. At 375 px and 1440 px, the page has no horizontal document overflow and all text controls remain reachable.
6. Escape closes dialogs and restores focus. Keyboard activation works without hover. Content remains visible with JavaScript disabled.
7. Readouts and synthetic actions must be marked as sample/demo content, not real financial, clinical, operational, or commercial claims.

## 6. Deliberate deviations

Two fully described fictional case studies rather than an unspecified original portfolio. No borrowed client work, stock photography, custom cursor, or real studio email. Native focus states replace pointer-only effects.

## 7. Documentation and testing

Create this site's README, adapted prompt, build log, and browser methodology. Link every decision to the source brief or explicitly identify it as an authored adaptation. Run structural validation, automated browser tests, accessibility scans, and desktop/mobile screenshots. Record actual outcomes, not assumed success. Do not describe tests or deployments as passing until they have run successfully.