GRIDO1
From prompt to page.
Every thousandth tells a story. An independent static interpretation of the archived GetLayers brief.
01 / Read the brief
The text source is 02-KIMI-F1-RACING-SYSTEMS.md. Reference media could not be inspected in this environment. This is not a pixel-identical reconstruction.
02 / Establish a visual system
Background #080b0d, foreground #f4f6f8, accent #00f59b, surface #12181b. Local fonts, a responsive 1320 px maximum grid, and a site-specific hero composition establish the hierarchy.
03 / Build the signature mechanism
A constructed helmet (flattened sphere shell, dark curved visor, trim, and lower guard) uses metallic mint lighting. Pointer movement reveals a wireframe shell rather than a real portrait. A real SVG path length drives the lap-position marker and deterministic speed/gear/G-force readouts.
04 / Make it interactive
- Scrub to 50% and confirm marker, speed, gear, and G-force update
- Run a lap and confirm completion returns the button to enabled
- Check the independent-study disclaimer
05 / Record the adaptations
No licensed driver portrait or helmet texture was available. Helmet/wireframe inspection replaces portrait burn-off. Circuit geometry and telemetry are illustrative, not race-accurate; no live standings or endorsements.
Shared architecture: local Three.js, native scrolling, a single frame scheduler, capped pixel density, offscreen/hidden-tab suspension, reduced-motion support, CSS fallback, and no backend.
06 / Validate honestly
See the actual validation record for test results. Automated checks do not replace manual screen-reader testing or reference-image comparison. All readouts and submissions are illustrative and local.
07 / Reproduce the build
python3 -m http.server 8080 --bind 0.0.0.0 # Open /getlayersai/sites/kimi/ cd getlayersai python3 tools/build.py python3 tools/verify.py npm ci npm test
Edit this site's record in tools/catalog.py before rebuilding. Shared rendering and interactions are in shared/scenes.js and shared/interactions.js. Generated HTML and documentation will be overwritten on regeneration.