跳到正文
VibeFather
免费注册

用这个模板做的 2 个案例

同一份提示词,不同的 [VARIABLES] 变量。点一个在上方预览。

关于这个模板

喷气发动机交互式讲解是一个单页工程课程,围绕原创的程序化 Three.js 涡扇发动机构建,而非下载的模型或视频。默认案例展示 Aerofield Lab 的 AF-09 高涵道比发动机,面向工程专业学生。它也适合教育工作者、博物馆团队、技术创作者和航空传播者,用来展示空气如何穿过机器,以及每个主要阶段如何贡献推力。

首屏将大型旋转发动机与简洁介绍和可操作的油门并排呈现。在主滚动序列中,短舱和核心机匣分五个状态打开:完整发动机、风扇与涵道、压气机、燃烧室、涡轮与排气。冷的涵道粒子、独立的核心气流和加热的排气让两条气流路径清晰可见。风扇和低压部件共享一个视觉转子转速,而高压转子转得更快,帮助访客将轴与它们驱动的部件联系起来。

油门实验室将旋转、气流和说明读数整合到一个同步控件中。四个阶段指南链接回导览中的精确位置,一个简短的知识检查将页面从视觉展示转变为可用的课程。Space Grotesk 标题、Inter 正文、等宽仪表字体、石墨色表面以及青色和琥珀色点缀,营造出清晰的技术展陈感,而没有拥挤的驾驶舱美学。

一切均由原创的 Three.js 图元、实例化叶片几何体、粒子和内联 SVG 绘制而成。无需照片、CAD 文件、纹理或生成的图像。五个变量可更改品牌、发动机类型、受众、操作标签和型号标识;一个备选涡桨案例展示了相同结构如何讲解另一种发动机。成品网站是静态的、响应式的、键盘可访问的、触摸友好的,并且在减少动态效果或无 WebGL 的情况下仍可使用。

模板提示词

在线演示就是用这份提示词原样做出来的,没有额外补充。其他案例只是改了 [VARIABLES] 变量的值。 提示词保持英文原版,国内常用的 AI 编程工具都能直接理解;下面附中文参考译文。

# Jet Engine Interactive Explainer

Build this website exactly as described below. Replace the [VARIABLES] with your own values; keep everything else.

## Brief
Build a one-page interactive engineering explainer for [BRAND]'s [ENGINE] ([MODEL_ID]), aimed at [AUDIENCE]. The default is an original high-bypass turbofan modeled entirely from Three.js primitives and custom blade geometry. A large working engine leads into five scroll-driven cutaway states covering the fan and bypass, compressor, combustor, and turbine with exhaust. A synchronized throttle changes two coaxial spool groups and directional airflow particles. When variable values change, redesign the procedural engine architecture, stage data, captions, guide, and quiz to fit the new [ENGINE] while preserving the layout, interaction model, and visual system.

- Audience: [AUDIENCE], plus educators, museum interpreters, technical creators, and aviation enthusiasts who need a clear visual explanation without CAD software or prior thermodynamics knowledge. The default copy welcomes engineering students and explains specialist terms in plain language.
- Goal: Help visitors identify the major engine stages, trace bypass and core airflow, connect each turbine to the components it drives, and test their understanding. The primary action, [PRIMARY_CTA], enters the scroll tour. A persistent throttle and motion pause control make cause and effect inspectable rather than a passive animation.
- Tone: Precise, curious, calm, and educational. Use short declarative explanations, concrete mechanical relationships, and honest labels for simplified sample data. The page should feel like a carefully art-directed engineering exhibit, not an aircraft cockpit, military interface, game HUD, or generic technology landing page.

## Stack
- Framework: Vite 6 + React 19 + TypeScript
- Styling: Vanilla CSS
- Libraries: three (MIT), lucide-react (ISC), @fontsource/space-grotesk (OFL), @fontsource/inter (OFL), @fontsource/ibm-plex-mono (OFL)
- Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs.
- Setup:
  - Use Vite with React and TypeScript. Set base: './' and build.sourcemap: false in vite.config.ts; the production command must emit only static files to dist/. Do not substitute another framework, renderer, styling system, physics engine, or state library.
  - Install and import three, lucide-react, and the three listed Fontsource packages locally. Import OrbitControls and RoomEnvironment from three/examples/jsm; use PMREMGenerator with RoomEnvironment for metallic reflections instead of downloading an HDRI.
  - Create src/content.ts as the single source for resolved variable values, navigation labels, hero copy, tour states, geometry parameters, stage records, airflow explanations, quiz questions, and footer copy. Include the default [BRAND], [ENGINE], [AUDIENCE], [PRIMARY_CTA], and [MODEL_ID] values there, rewrite all engine-specific content when those values change, and never leave square-bracket variable tokens visible in the rendered site.
  - Build the default engine along the X axis from original lathed nacelle and casing bands, an exhaust cone, two coaxial shafts, 22 wide fan blades, three low-pressure and six high-pressure compressor rotor rows with static stator rows between them, an annular combustor with 12 small fuel-nozzle markers, one high-pressure turbine row, and three low-pressure turbine rows. Use custom tapered, slightly twisted BufferGeometry blades and InstancedMesh for repeated blades. Keep the model recognizably turbofan-like but do not copy any real engine or CAD design.
  - Use MeshStandardMaterial for titanium, steel, and dark casing, a neutral procedural environment, one broad key light, a cooler rim light, and a code-generated contact-shadow plane. Enable antialiasing and alpha; cap pixel ratio at 1.6 on desktop and 1.35 on mobile. Use one Points geometry for 160 desktop or 80 mobile airflow particles with deterministic seeded paths, and pause requestAnimationFrame work while the scene is offscreen or the document is hidden.
  - Keep one shared React engine state: throttle, motionPaused, showCoreFlow, showBypassFlow, scrollProgress, activeStage, selectedStage, and controlMode. At throttle 0 all rotors and particles stop; at throttle 1 the N1 fan, low-pressure compressor, and low-pressure turbine rotate at 4.8 radians per second while the N2 high-pressure compressor and turbine rotate at 12.5 radians per second. Interpolate linearly between those endpoints and label the 2.6:1 relationship as a visual teaching ratio, not measured RPM. Drive particle velocity from the same throttle value.
  - Create a reusable EngineScene component for the hero, tour, and lab, with shared geometry definitions and only the visible scene rendering. Provide an original inline SVG longitudinal cutaway as a no-WebGL fallback, including intake, fan, compressor, combustor, turbine, bypass duct, exhaust, and stage labels; all controls must still update the HTML readouts when WebGL is unavailable.
  - Use Lucide icons only for ArrowDown, Play, Pause, RotateCcw, Gauge, Wind, Layers3, Check, X, ChevronRight, and Menu. Give every icon button an accessible text label and 44px minimum touch targets.
  - Centralize responsive rules and keyframes in src/styles.css. Support 1440×900 and 390×844 without horizontal overflow or console errors, include visible keyboard focus, and implement prefers-reduced-motion by stopping continuous rotor and particle movement, removing camera easing and entrance animation, and retaining instant cutaway states, manual controls, quiz feedback, and all explanatory content.

## Variables
- [BRAND] — Brand (default: "Aerofield Lab"). Invented educational studio or engineering lab name used in the header, lesson copy, and footer.
- [ENGINE] — Engine subject (default: "High-Bypass Turbofan"). An air-breathing engine that can be modeled from code and divided into four meaningful teaching stages.
- [AUDIENCE] — Audience (default: "engineering students"). Lowercase descriptive audience phrase that fits naturally after for in the hero copy.
- [PRIMARY_CTA] — Primary action (default: "Explore the engine"). Short button label that scrolls to the engine tour and remains suitable for the selected subject.
- [MODEL_ID] — Model identifier (default: "AF-09"). Short invented alphanumeric identifier used in technical labels and the lesson recap, never a real engine designation.
- [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/jet-engine-interactive-explainer 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 模板

解锁完整提示词和源码

  • 完整提示词:设计、版块、动效、素材
  • 每个在线演示的源码
  • 商用授权

在线演示和 DESIGN.md 仍然免费。

$9/月起 · 年付和终身正在上线特惠

DESIGN.md

单独的设计规范:配色、字体、间距和动效。可以把这套视觉用到你已有的项目上。

---
name: "Jet Engine Interactive Explainer"
colors:
  deep_hangar: "#080B10"
  instrument_panel: "#10161D"
  raised_graphite: "#17212B"
  frost: "#EDF3F6"
  cool_gray: "#92A3AD"
  blueprint_line: "#283642"
  flow_cyan: "#62D7F2"
  combustion_amber: "#FF9A4D"
  brushed_titanium: "#A9B4BA"
  gunmetal: "#4C5A64"
typography:
  display_and_section_headings: { family: "Space Grotesk", weights: [500, 600, 700] }
  body_buttons_guide_rows_and_quiz_answers: { family: "Inter", weights: [400, 500, 600] }
  eyebrows_model_ids_airflow_labels_and_instrument_readouts: { family: "IBM Plex Mono", weights: [400, 500] }
spacing: "Use an 8px base unit, a maximum content width of 1520px, 32px desktop gutters, and 20px mobile gutters. Desktop section padding is 120px 0; mobile is 76px 0. Use a 12-column desktop grid with 24px gaps. Keep body measure between 52 and 68 characters, control gaps at 10–12px, and stage-row padding at 24px 0."
radius: "Use 3px on buttons and inputs, 8px on scene panels and inspectors, and no rounding on major sections or stage-guide rows. Reserve pills for compact airflow legends and circles for transport icon buttons."
---

# Jet Engine Interactive Explainer — 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
- **Deep hangar** `#080B10` — Page background and canvas clear color.
- **Instrument panel** `#10161D` — Header, stage inspector, lab controls, and quiz surfaces.
- **Raised graphite** `#17212B` — Control groups, selected rows, and subtle scene panels.
- **Frost** `#EDF3F6` — Primary headings, important values, and high-contrast body copy.
- **Cool gray** `#92A3AD` — Secondary copy and inactive labels; never use for text smaller than 13px.
- **Blueprint line** `#283642` — Hairline borders, construction grid, table rules, and leader lines.
- **Flow cyan** `#62D7F2` — Primary action, bypass airflow, active stage, focus outline, and progress only.
- **Combustion amber** `#FF9A4D` — Combustor, heated core particles, and exhaust highlights only.
- **Brushed titanium** `#A9B4BA` — Three.js blades and bright machined surfaces, with darker variants for depth.
- **Gunmetal** `#4C5A64` — Three.js shafts, casings, stators, and secondary metal surfaces.

## Typography
- **Display and section headings** — Space Grotesk (OFL), weights 500/600/700. Self-host the font files.
- **Body, buttons, guide rows, and quiz answers** — Inter (OFL), weights 400/500/600. Self-host the font files.
- **Eyebrows, model IDs, airflow labels, and instrument readouts** — IBM Plex Mono (OFL), weights 400/500. Self-host the font files.

## Spacing & shape
- Spacing: Use an 8px base unit, a maximum content width of 1520px, 32px desktop gutters, and 20px mobile gutters. Desktop section padding is 120px 0; mobile is 76px 0. Use a 12-column desktop grid with 24px gaps. Keep body measure between 52 and 68 characters, control gaps at 10–12px, and stage-row padding at 24px 0.
- Radius: Use 3px on buttons and inputs, 8px on scene panels and inspectors, and no rounding on major sections or stage-guide rows. Reserve pills for compact airflow legends and circles for transport icon buttons.

## Motion
- On hero entry, fade the copy upward by 14px over 420ms and ease the engine from scale 0.97 and opacity 0 to its final state over 560ms. Rotors and airflow then follow the throttle continuously; there is no separate idle camera spin or decorative background animation.
- Drive every cutaway directly from normalized scroll progress through five explicit keyframes. Interpolate casing opacity, hinge rotation, stage highlight, camera position, and label visibility from the same keyframe records so scrolling cannot drift from the visible engine state.
- Rotate the N1 and N2 groups around the engine X axis at their specified relative speeds. Keep stators, combustor, shafts, and nacelle stationary. Clamp frame delta after tab restoration and use deterministic particle wrapping so returning to the page never causes a jump or burst.
- Enable OrbitControls damping at 0.08 with zoom limited to 0.8×–1.65× of the default camera distance and polar angle limited to 35°–110°. Reset view restores camera, target, and selected stage over 240ms without changing throttle or scroll progress.
- Airflow particles follow two separate deterministic longitudinal paths: the larger bypass annulus remains outside the core and rejoins behind it, while the core stream narrows through compressor rows, expands and shifts from cyan to amber in the combustor, then accelerates through turbine and exhaust. Hide each stream immediately when its legend toggle is off.
- Buttons, stage disclosures, labels, and quiz feedback use 160ms opacity and 2–4px transform transitions. Avoid glitch effects, camera shake, excessive bloom, lens flares, arbitrary part explosions, and unrelated parallax.
- For prefers-reduced-motion, stop rotor and particle loops, remove smoothing and entrance transitions, and update scroll scenes to discrete keyframe states instantly. Throttle changes still update numeric readouts and static flow-path emphasis, and the complete lesson remains usable without animation.

## Imagery
The only hero visual is an original, high-craft procedural Three.js [ENGINE], shown large in three-quarter view with machined metal, a restrained construction grid, fine stage callouts, and a soft contact shadow. The default turbofan must be recognizable immediately through its wide front fan, long nacelle, coaxial compressor and turbine rows, central shafts, annular combustor, and exhaust cone. Casing wedges open progressively to reveal the interior. No photographs, AI-generated images, downloaded 3D models, HDRIs, texture maps, logos, people, or branded objects are used. HTML labels and an SVG leader-line overlay track projected 3D anchors; Lucide supplies only interface icons.

## Tone
Precise, curious, calm, and educational. Use short declarative explanations, concrete mechanical relationships, and honest labels for simplified sample data. The page should feel like a carefully art-directed engineering exhibit, not an aircraft cockpit, military interface, game HUD, or generic technology landing page.

---
Inspired by Kimi 3D Make Showcase — https://www.kimi.com/showcases/3dmake
— Prompt by VibeFather · https://vibefather.ai/t/jet-engine-interactive-explainer · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

改成你自己的

  • 大学航空航天系:将 BRAND 设为你的实验室名称,ENGINE 设为你的教学涡扇发动机,AUDIENCE 设为一年级机械工程学生。
  • 科学博物馆展览团队:保留涡扇发动机,将 PRIMARY_CTA 设为开始导览,并将阶段指南指向适合自助终端的触摸布局。
  • 技术内容创作者:将 BRAND 设为你的频道,ENGINE 设为涡桨发动机,并重写测验以匹配你受众的水平。
  • 航空培训机构:将 MODEL_ID 设为你的课程发动机代码,AUDIENCE 设为维修学员,并根据你的教学大纲调整阶段说明文字。

喷气发动机交互式讲解:常见问题

喷气发动机交互式讲解如何展示空气如何穿过涡扇发动机?

喷气发动机交互式讲解通过三股粒子流让气流可见:核心机周围的冷涵道粒子、穿过压气机和燃烧室的独立核心气流,以及离开涡轮的加热排气。滚动时,短舱和核心机匣分五个状态打开,油门实验室将粒子速度与旋转转子的同一控件绑定,因此访客可以看到每个阶段如何贡献推力。

如果访客的浏览器无法运行 WebGL,喷气发动机交互式讲解还能用吗?

喷气发动机交互式讲解模板包含一个原创的内联 SVG 纵向剖面图作为无 WebGL 回退方案,显示进气道、风扇、压气机、燃烧室、涡轮、涵道、排气和阶段标签。当 WebGL 不可用时,所有控件仍会更新 HTML 读数,并且模板通过停止连续的转子和粒子运动来遵循减少动态效果设置,同时保留即时剖面状态、手动控件、测验反馈和说明内容。

怎么用 AI 做一个喷气发动机交互式讲解?

复制本页的完整提示词(Pro),或者运行 npx vibefather add jet-engine-interactive-explainer,把 [BRAND]、[ENGINE]、[AUDIENCE]、[MODEL_ID] 换成你自己的内容,再粘贴到 Claude Code、Codex、Cursor 等 AI 编程工具里。在线演示就是用这份提示词原样做出来的。