2 cases built from this template
Same prompt, different [VARIABLES]. Click one to preview it above.About this template
This history explorer presents the Colosseum as a structure you can take apart. A warm limestone model appears immediately, with open arcades, rising seats, an arena floor and a network of spaces below it. Drag to inspect the outer walls, zoom toward the center or choose a feature from the accompanying list. The model and interface are built from code, so the example does not depend on a downloaded architectural asset.
A state slider follows the building from foundations through rising arches and a completed interpretation to a weathered ruin. The labels describe physical states rather than calendar years. A cutaway removes a front section and exposes how the seating, arena and underground routes fit together. Four learning stops explain the arena floor, hypogeum, seating tiers and shade canopy. Each moves the camera to a useful view and pairs the scene with a short note. Visitors can explore freely or follow a guided tour with pause, previous, next and exit controls.
The layout feels like a compact architectural exhibit. Mineral paper, fine rules, a readable serif and restrained technical labels frame the model without competing with it. On a phone, the stage, timeline and explanations become a natural vertical sequence with touch controls. Reduced motion keeps every learning feature available through immediate state changes.
The prompt suits educators, museum prototypes and architecture studies that need a spatial explanation rather than a long article. Change the studio name, exhibit title, audience and accent to make a separate edition. Copy and labels stay in one content module. The model clearly identifies reconstructed details as interpretive and its proportions as approximate, with a link to the archaeological park for further reading.
The template prompt
The live demo was built from exactly this text — nothing added. The other cases only change the values of the [VARIABLES].
# 3D Colosseum History Explorer Build this website exactly as described below. Replace the [VARIABLES] with your own values; keep everything else. ## Brief Build [BRAND], an original explorable exhibit titled [EDITION] for [AUDIENCE]. Use an entirely code-built Three.js Colosseum model, orbit/zoom, a construction-to-weathering state scrubber, four explanatory hotspots, a meaningful cutaway and a guided camera tour. - Audience: [AUDIENCE], museum visitors and anyone who learns spatial ideas by exploring. - Goal: Make the relationship between facade, seating, arena and service spaces understandable through direct manipulation. - Tone: Precise, curious, readable US English; distinguish observation from interpretation and label figures approximate. ## Stack - Framework: Vite + TypeScript - Styling: Vanilla CSS - Libraries: three (MIT), @fontsource/newsreader (OFL-1.1), @fontsource/dm-sans (OFL-1.1) - Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs. - Setup: - Install dependencies locally. Configure Vite base ./, build.sourcemap false and an npm run build script. - Create src/content.ts for variables, state explanations, hotspot copy, UI and source links. Rewrite edition/audience tone when variables change without changing the architectural subject. - Use Three.js OrbitControls from the installed package and original procedural meshes, CanvasTextures and shaders; no ready-made architectural assets. Render a settled high-quality model immediately. ## Variables - [BRAND] — Learning studio (default: "Stonefield Atlas") - [EDITION] — Exhibit title (default: "An amphitheater, unbuilt") - [AUDIENCE] — Visitors (default: "Curious minds and architecture students") - [ACCENT] — Interface accent (default: "#B58A50") - [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/3d-colosseum-history-explorer in the footer (default: yes; delete this line to remove it) The copy under Pages & Sections is written for the default values. If your values differ, rewrite every headline, paragraph, label and image for them — same length, tone and structure. Layout, colors, type and motion stay as described. Keep all copy, image paths and links in one content file (for example `src/content.ts`), keyed by section, so the content can be swapped later without touching components.
Pro template. The design, sections, motion and assets parts of this prompt are for Pro members. The live demo and DESIGN.md stay free.
DESIGN.md
The design system on its own — colors, type, spacing and motion. Apply this look to a project you already have.
---
name: "3D Colosseum History Explorer"
colors:
parchment: "#EEEAE0"
stone: "#C7B79B"
deep_stone: "#8F8068"
ink: "#303B38"
accent: "[ACCENT]"
rule: "#CFC9BA"
typography:
exhibit_titles: { family: "Newsreader", weights: [400, 500] }
body_and_interface: { family: "DM Sans", weights: [400, 500, 600] }
spacing: "8px unit; 24px outer desktop gutters, 20px mobile; 24px panel gaps. Stage gets most space. Header 72px; notes rail 300px. Body 15–17px with 1.5 line-height. Avoid tiny legend text."
radius: "2–4px controls; stage has clean square edges and fine border; notes are a rail, not pill cards."
---
# 3D Colosseum History Explorer — Design System
Apply this design system to an existing project. It describes the look and feel only; for the full site, use prompt.md.
## Colors
- **Parchment** `#EEEAE0` — Canvas and page ground
- **Stone** `#C7B79B` — Limestone model
- **Deep stone** `#8F8068` — Crevices and weathered masonry
- **Ink** `#303B38` — Readable text
- **Accent** `[ACCENT]` — Active features and section cut
- **Rule** `#CFC9BA` — Technical dividers
## Typography
- **Exhibit titles** — Newsreader (OFL), weights 400/500. Self-host the font files.
- **Body and interface** — DM Sans (OFL), weights 400/500/600. Self-host the font files.
## Spacing & shape
- Spacing: 8px unit; 24px outer desktop gutters, 20px mobile; 24px panel gaps. Stage gets most space. Header 72px; notes rail 300px. Body 15–17px with 1.5 line-height. Avoid tiny legend text.
- Radius: 2–4px controls; stage has clean square edges and fine border; notes are a rail, not pill cards.
## Motion
- Orbit and pinch zoom follow direct input with gently damped controls. No automatic orbit on load.
- State changes interpolate structure and materials over 350–600ms; slider follows user continuously.
- Hotspot/tour camera movement is 900ms smooth and cancelable. Reduced motion uses immediate updates and user-advanced tour stops.
## Imagery
All imagery is original code: layered elliptical masonry, true open arcades, stepped seating, arena planks, below-floor corridor network, canopy panels/masts and procedural limestone grain. No photography or downloaded models. Clear warm daylight, subtle shadows and grounded geometry must supply a high-craft visual anchor on the first screen.
## Tone
Precise, curious, readable US English; distinguish observation from interpretation and label figures approximate.
---
Inspired by Code-built amphitheater in a reasoning-effort study by @Paras Tiwari — https://spectrumailab.com/blog/gpt-6-1-sol-reasoning-effort-test-2026
— Prompt by VibeFather · https://vibefather.ai/t/3d-colosseum-history-explorer · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown
Make it yours
- A university classics department: set [BRAND] to the faculty, make [EDITION] a course exhibit, and rewrite the four learning stops for your syllabus topics.
- A city archaeology museum: use [BRAND] as the museum name, tune [ACCENT] to your signage, and link the source note to your own collection page.
- An architecture studio teaching spatial analysis: set [AUDIENCE] to first-year students and rewrite the state labels to match your own construction phases.
- A heritage tourism board: set [EDITION] to a visitor exhibit, keep the guided tour for walk-in audiences, and point the further reading link to local site information.
3D Colosseum History Explorer: questions and answers
How do I change the studio name, exhibit title and audience on the 3D Colosseum History Explorer?
The 3D Colosseum History Explorer template keeps four variables in one content module: BRAND for the learning studio name, EDITION for the exhibit title, AUDIENCE for who the exhibit addresses, and ACCENT for the interface color. Set those values and rewrite every headline, paragraph and label to match, keeping the same length and tone. The architectural subject stays the Colosseum.
What does the construction state slider in the 3D Colosseum History Explorer actually show?
The 3D Colosseum History Explorer template includes a state scrubber that moves the model from foundations through rising arches and a completed interpretation to a weathered ruin. The labels describe physical states rather than calendar years, so no dates appear. Each state pairs the model with a short explanation, and the cutaway stays available as the structure changes.
What are the four learning stops in the 3D Colosseum History Explorer?
The 3D Colosseum History Explorer template includes four learning stops covering the arena floor, the hypogeum below it, the seating tiers and the shade canopy. Selecting a stop moves the camera to a useful view and shows a short note beside the scene. Visitors can explore freely or follow a guided tour with pause, previous, next and exit controls.
Can I adapt the 3D Colosseum History Explorer for a museum prototype or a classroom?
The 3D Colosseum History Explorer template suits educators, museum prototypes and architecture studies that need a spatial explanation rather than a long article. Set BRAND to your institution, EDITION to the exhibit name and AUDIENCE to your visitors or students, then rewrite the state and hotspot copy in the single content module. The model labels reconstructed details as interpretive and proportions as approximate.
Does the 3D Colosseum History Explorer need downloaded 3D models or external services to run?
The 3D Colosseum History Explorer template builds the entire amphitheater from code using Three.js, with original procedural meshes, canvas textures and shaders rather than a downloaded architectural asset. The stack is Vite, TypeScript and Vanilla CSS with no backend, no server code and no external APIs, and the build outputs static files you can host anywhere. A settled high-quality model renders immediately on load.
How do I build a 3D colosseum history explorer with AI?
Copy the full prompt (Pro) from this page or run npx vibefather add 3d-colosseum-history-explorer, replace [BRAND], [ACCENT], [EDITION] and [AUDIENCE] with your own content, and paste it into Claude Code, Codex, Cursor or another AI coding agent. The live demos were built from exactly that text.
Which AI model built the 3D Colosseum History Explorer demo?
The Architectural field study case was built by GPT-6.1 Sol in Codex; the Museum learning edition case was built by GPT-6.1 Sol in Codex. Each build used the published prompt with nothing added.
What tech stack and pages does the 3D Colosseum History Explorer template use?
3D Colosseum History Explorer is a single-page site built with Plain HTML and Three.js, with drag & physics, 3d / webgl and micro-interactions. The prompt fixes the stack so every AI tool builds the same kind of project, and the result runs as a static site you can host anywhere.
Is the 3D Colosseum History Explorer template free to use?
3D Colosseum History Explorer is a Pro template: the brief, stack and variables are public, and the full prompt, the source code of the live demo and a commercial license come with VibeFather Pro. Its DESIGN.md is free for personal projects.
Does the 3D Colosseum History Explorer template work on mobile?
Yes. Every 3D Colosseum History Explorer build was tested on a phone-sized screen as well as desktop before it went live, checking layout, text size and touch targets. Open the live demo on your phone, or switch the preview on this page to mobile view, to check it yourself.