跳到正文
VibeFather
免费注册

用这个模板做的 2 个案例

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

关于这个模板

交互式产品导览页是一个单页 SaaS 网站,核心是一个可运行、代码绘制的产品演示,而不是静态截图。分栏首屏介绍产品,并在旁边放置一个完整的引导式工作区。三个章节标签引导访客完成九个聚焦步骤,配有锚定热点、遮罩聚光灯、简洁提示框、进度控制、可选的自动播放,以及每章结束后的转化提示。交互支持鼠标、触摸和键盘,移动端将引导内容移到界面下方,避免变成微小的桌面模拟图。

视觉系统将暖纸色、编辑风格衬线标题和珊瑚色引导标记与深墨色应用画布搭配。适合需要快速说明工作流程并为潜在客户提供有用下一步的 SaaS 创始人、产品营销人员和独立团队。导览下方包含章节卡片、决策路径功能区块、实用 FAQ 和最终行动号召,让页面完整而不稀释演示。章节完成状态为上下文下一步创造自然停顿,手动导航则让回访者直接跳到最关心的流程。

默认内容围绕 Nookline——一个面向创意工作室的客户审批工作区。替换四个变量即可重新定位到其他产品和受众;所有界面标签、步骤、示例项目和行动号召都集中管理以便重写。另一个物业护理案例展示了相同结构在不同行业的应用。所有内容均使用 React、CSS、SVG 和 Lucide 图标绘制,没有照片、远程 API 或后端。动效克制并支持减少动态效果,静态构建将字体和其他所有资源保留在本地。

模板提示词

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

# Interactive Product Tour Page

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

## Brief
Build an original single-page product tour for [BRAND], a [PRODUCT] for [AUDIENCE]. The page sells through demonstration: a large, fully code-drawn application sits in the hero and guides visitors through three workflow chapters and nine concrete steps. Every chapter ends with a useful recap and a [PRIMARY_CTA] conversion action.

- Audience: SaaS founders, product marketers, and independent software teams who need to explain a multi-step workflow, qualify prospects, and make a product feel understandable before a signup or sales call.
- Goal: Let visitors complete a clear interactive tour at their own pace or with optional autoplay, understand the product's core workflow, and respond to a contextual call to action without leaving the page.
- Tone: Assured, practical, and quietly editorial. Use short sentences, precise product language, and believable sample details; avoid hype, fake customer claims, generic AI phrasing, and jokes.

## Stack
- Framework: Vite 6 + React 19 + TypeScript
- Styling: Tailwind CSS 4
- Libraries: motion (MIT), lucide-react (ISC), @fontsource-variable/newsreader (OFL), @fontsource-variable/manrope (OFL), @fontsource/ibm-plex-mono (OFL)
- Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs.
- Setup:
  - Configure vite.config.ts with base: './', build.sourcemap: false, and the Tailwind CSS Vite plugin; the production output is static files in dist/.
  - Import Newsreader Variable, Manrope Variable, and IBM Plex Mono from their local Fontsource packages; do not add a font stylesheet URL.
  - Keep every visitor-facing string, variable value, navigation label, chapter, tooltip, sample project, FAQ, dialog label, and link in src/content.ts. Keep typed tour-step definitions there as well, including targetId and tooltip placement.
  - Implement the tour in src/components/ProductTour.tsx as one explicit state machine: activeChapter, activeStep, chapterComplete, and playbackState ('idle' | 'playing' | 'paused'). Render the original application scenes in src/components/AppCanvas.tsx and resolve hotspot targets through refs or data-tour-target attributes.
  - Define the exact color, type, spacing, radius, shadow, and keyframe tokens in src/index.css and the Tailwind theme. Use Motion for step, panel, dialog, and section transitions; use ordinary React state for application-demo changes.
  - Use a native dialog element for the client-side conversion dialog, including labelled fields, Escape dismissal, focus return, and a local success state. Do not transmit or persist form values.
  - Provide development, build, and preview scripts in package.json. The fixed default build command is npm run build; do not introduce a server, router, state library, or additional component library.

## Variables
- [BRAND] — Invented product brand (default: "Nookline"). Use a short invented name in the wordmark, page title, product copy, dialog, and footer.
- [PRODUCT] — Product category (default: "client approval workspace"). A lowercase description of the product; rewrite the workflow, interface labels, and sample data to suit it.
- [AUDIENCE] — Primary customer audience (default: "independent creative studios"). A plain lowercase audience description used in the hero and supporting copy.
- [PRIMARY_CTA] — Primary call to action (default: "Start a free workspace"). Use the same action in the header, chapter-completion panels, and final CTA; it opens the local demo dialog.
- [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/interactive-product-tour-page 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: "Interactive Product Tour Page"
colors:
  paper: "#F4F1EA"
  surface: "#FFFCF7"
  ink: "#18201F"
  muted: "#69716C"
  line: "#D9D8D0"
  stage: "#111A1D"
  stage_raised: "#1B272B"
  stage_text: "#F4F6F2"
  coral: "#FF7058"
  coral_deep: "#A9382B"
  mint: "#B8D8C5"
typography:
  editorial_display: { family: "Newsreader Variable", weights: [400, 500, 600] }
  interface_and_body: { family: "Manrope Variable", weights: [400, 500, 600, 700] }
  step_counts_and_compact_data: { family: "IBM Plex Mono", weights: [400, 500] }
spacing: "Use an 8px base grid. Content max-width is 1360px with 64px desktop gutters, 32px tablet gutters, and 20px mobile gutters. Header height is 72px. Hero top/bottom padding is 56px/96px on desktop and 32px/64px on mobile. Later sections use 112px desktop and 72px mobile vertical padding. Keep text measures near 58 characters and application labels compact."
radius: "Use 18px for the tour console and dialog, 14px for large feature panels, 10px for application panels and inputs, and 7px for buttons. Reserve full pills for status chips, progress counts, and small tab labels. Use one-pixel borders rather than a page full of floating cards; only the tour console gets a large shadow: 0 24px 80px rgba(17, 26, 29, 0.14)."
---

# Interactive Product Tour Page — 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
- **Paper** `#F4F1EA` — Main page background and generous editorial margins
- **Surface** `#FFFCF7` — Header, chapter cards, FAQ panels, and dialog surfaces
- **Ink** `#18201F` — Primary text, dark buttons, and strong icon strokes
- **Muted** `#69716C` — Secondary copy and inactive controls on light surfaces
- **Line** `#D9D8D0` — Hairline borders, separators, and inactive progress tracks
- **Stage** `#111A1D` — Main application-canvas background
- **Stage Raised** `#1B272B` — Application sidebar, cards, menus, and tooltip surfaces
- **Stage Text** `#F4F6F2` — Primary text inside the dark product mockup
- **Coral** `#FF7058` — Active hotspot, progress, selected tabs, and primary accent fills; pair with Ink text on light backgrounds
- **Coral Deep** `#A9382B` — Accessible accent text and focus rings on Paper and Surface
- **Mint** `#B8D8C5` — Approval, resolved, and success states inside the application

## Typography
- **Editorial display** — Newsreader Variable (OFL), weights 400/500/600. Self-host the font files.
- **Interface and body** — Manrope Variable (OFL), weights 400/500/600/700. Self-host the font files.
- **Step counts and compact data** — IBM Plex Mono (OFL), weights 400/500. Self-host the font files.

## Spacing & shape
- Spacing: Use an 8px base grid. Content max-width is 1360px with 64px desktop gutters, 32px tablet gutters, and 20px mobile gutters. Header height is 72px. Hero top/bottom padding is 56px/96px on desktop and 32px/64px on mobile. Later sections use 112px desktop and 72px mobile vertical padding. Keep text measures near 58 characters and application labels compact.
- Radius: Use 18px for the tour console and dialog, 14px for large feature panels, 10px for application panels and inputs, and 7px for buttons. Reserve full pills for status chips, progress counts, and small tab labels. Use one-pixel borders rather than a page full of floating cards; only the tour console gets a large shadow: 0 24px 80px rgba(17, 26, 29, 0.14).

## Motion
- On step changes, crossfade and translate the outgoing/incoming guidance by 8px over 240ms; animate the spotlight cutout and target outline to the new bounds over 200ms without changing the console's dimensions.
- Show a restrained 2-second coral box-shadow pulse on the active numbered hotspot. Stop the pulse while autoplay is paused by manual interaction and remove it entirely for reduced motion.
- Autoplay is off on initial load. When explicitly started, each step displays for 5000ms while a thin coral progress line fills linearly; chapter completion always pauses playback.
- Reveal lower sections once with a 20px rise and 420ms fade, staggered by 70ms. Do not pin the page, hijack scrolling, or run decorative continuous background animation.
- Open the native dialog with a 180ms opacity and 0.98-to-1 scale transition. Respect prefers-reduced-motion by removing transforms, pulses, smooth scrolling, and reveal delays, and by leaving autoplay unavailable while retaining every manual control.

## Imagery
There are no raster images. The visual anchor is a rich, original product interface built from semantic HTML, CSS, inline SVG, and Lucide icons: sidebar, queue, file canvas, comment pins, version controls, approval checklist, progress indicators, and handoff ledger. Draw a simple generic three-panel brand mark and abstract file thumbnails in code. No screenshots, stock photographs, customer logos, mascot, signature illustration, or recognizable existing product interface.

## Tone
Assured, practical, and quietly editorial. Use short sentences, precise product language, and believable sample details; avoid hype, fake customer claims, generic AI phrasing, and jokes.

---
— Prompt by VibeFather · https://vibefather.ai/t/interactive-product-tour-page · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

改成你自己的

  • 金融科技入门工具:将 BRAND 设为你的平台,围绕账户设置和验证重写九个导览步骤,并将 PRIMARY_CTA 指向演示请求。
  • 独立分析产品:保留章节标签,但将示例项目换成你的仪表盘,并重写提示框以解释每个图表和筛选器。
  • B2B 排程 SaaS:将 PRODUCT 改为排程,把审批流程替换为预约步骤,并将 PRIMARY_CTA 设为免费试用注册。
  • 物业护理服务:参考备用的住宅案例,将章节重命名为服务访问和报告,并重写维护任务的示例数据。

交互式产品导览页:常见问题

交互式产品导览页模板是什么?包含哪些内容?

交互式产品导览页模板是一个单页 SaaS 网站,核心是一个可运行、代码绘制的产品演示。它包含带引导式工作区的分栏首屏、覆盖九个步骤的三个章节标签、锚定热点、遮罩聚光灯、提示框、进度控制、可选的自动播放,以及每章结束后的转化提示。导览下方有章节卡片、决策路径功能区块、实用 FAQ 和最终行动号召。

如何将 Nookline 演示内容换成我自己的 SaaS 产品?

在提示词中将 BRAND、PRODUCT、AUDIENCE 和 PRIMARY_CTA 四个变量设为你的值,然后重写每个界面标签、导览步骤、示例项目、提示框和行动号召以匹配你的工作流程。所有面向访客的字符串都集中在一个内容文件中,因此无需改动导览逻辑或代码绘制的应用场景即可替换文案。

哪些 AI 编程工具可以构建交互式产品导览页?

交互式产品导览页演示由 Kimi K3.1 Pro 在 Kimi Code 中构建,以及由 DeepSeek V4.1 Flash 在 DeepSeek Harness 中构建。你也可以将发布的提示词粘贴到 Claude Code、Codex、Cursor、GitHub Copilot、Windsurf 或 Gemini CLI 中。提示词指定了 Vite、React、TypeScript、Tailwind CSS、Motion 和 Lucide 图标,并要求无后端的静态构建。