跳到正文
VibeFather
免费注册

用这个模板做的 2 个案例

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

关于这个模板

团队聊天应用界面是一个可实际运行的客户端消息工作区,而不是静态的仪表盘模型。它直接打开一个繁忙的项目频道,首屏同时展示频道侧边栏、可读的对话内容和成员目录。该布局适合设计工具、效率产品、协作应用,以及需要展示可信 UI 状态的作品集项目。

视觉系统将温暖的米白色表面与克制的紫罗兰色点缀、紧凑的 Manrope 标题和高度可读的 Inter 正文搭配在一起。协调的深色主题会改变每个面板、边框、图标、头像和弹出层,而不是简单地反转页面。几何 SVG 肖像为虚构团队赋予人的存在感,无需外部照片。消息保持全宽且安静;颜色仅用于在线状态、未读计数、表情回应和输入框操作。

频道切换、消息搜索、表情回应切换、回复话题串、成员筛选、提及、emoji 选择和消息发送均可在浏览器中工作。草稿、新消息、表情回应、已读状态和主题偏好会保存在 localStorage 中,而响应式布局会在较小屏幕上将两个侧边栏变为可访问的抽屉。减少动态效果的偏好设置和键盘控制也是规范的一部分。

默认内容讲述一个独立设计工作室协调笔记本重新设计的故事。四个变量可更改应用品牌、工作区、团队类型和项目,使同一结构可以变成烘焙团队规划季节性发布、研究小组或其他团队。所有示例对话、角色、频道名称和项目细节均根据这些值编写,并保存在一个内容文件中。技术栈为 Vite、React、TypeScript、Tailwind CSS、Lucide 图标和自托管的 Fontsource 字体,无需后端或外部资源。

模板提示词

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

# Team Chat App Interface

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

## Brief
Build a single-screen, fully interactive team chat application for [BRAND], set inside [WORKSPACE], a [TEAM_TYPE] collaborating on [PROJECT]. The first viewport is the actual product, not a marketing landing page: a channel sidebar, a dense but calm message thread, and a member directory share one polished workspace. All people, organizations, conversations, and project details are fictional and original.

- Audience: Designers and developers building collaboration software, product teams that need a realistic messaging UI, and people looking for a substantial React app interface rather than a static visual mockup.
- Goal: Let a visitor switch channels, search and send messages, toggle reactions, open and answer thread replies, insert mentions and Unicode emoji, filter members, and switch between dark and light themes. Keep all changes in React state and localStorage so the complete experience works as static files with no network service.
- Tone: Warm, focused, and quietly playful. Use concise, believable workplace messages with specific decisions and helpful responses; avoid corporate slogans, forced enthusiasm, and generic lorem ipsum.

## Stack
- Framework: Vite 5 + React 18 + TypeScript
- Styling: Tailwind CSS 3.4
- Libraries: lucide-react (ISC), @fontsource-variable/manrope (OFL), @fontsource-variable/inter (OFL)
- Build: `npm run build` → static files in `dist/`. No backend, no server code, no external APIs.
- Setup:
  - Set Vite base to './', build.outDir to 'dist', and build.sourcemap to false; the production output must be fully static and portable.
  - Configure Tailwind with a class-based dark strategy and semantic color tokens backed by CSS variables; define the complete light and dark palettes in src/index.css.
  - Keep all editable interface labels, channel names, member profiles, sample messages, reactions, and thread replies in src/content.ts, organized by workspace and channel and written for the supplied variable values.
  - Use React useReducer for workspace state and small presentational components for the sidebar, message list, composer, thread, member directory, and overlays; do not add a router or a state-management dependency.
  - Persist theme, per-channel drafts, sent messages, reactions, thread replies, and cleared unread counts under one localStorage key derived from the slugified [BRAND]; include a clearly labeled Reset local demo action in the workspace menu.
  - Use a textarea for the composer and native buttons for every action, with visible focus rings, accessible names, Escape-to-close behavior, and focus return when popovers or drawers close.

## Variables
- [BRAND] — Chat product name (default: "Plumthread"). Use a short invented product name and derive its lowercase slug for the document title and localStorage key.
- [WORKSPACE] — Workspace name (default: "Fable & Fern Studio"). Name the fictional organization shown at the top of the channel sidebar.
- [TEAM_TYPE] — Team description (default: "independent product design studio"). Adapt member roles, channel names, and workplace vocabulary to this kind of team.
- [PROJECT] — Current shared project (default: "Wander notebook redesign"). Make the selected channel, pinned note, and sample conversation center on this project.
- [CREDIT] — keep a small "Template by VibeFather" link to https://vibefather.ai/t/team-chat-app-interface 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.

## Design
### Colors
- Light canvas `#F4F3F7` — Overall app background and narrow gutters behind the workspace.
- Light surface `#FFFFFF` — Conversation pane, composer, search fields, and primary controls.
- Light sidebar `#ECEAF2` — Channel sidebar and member directory background.
- Light hover `#F7F5FA` — Message-row hover, selected subtle surfaces, and reaction-chip background.
- Light text `#25222C` — Primary headings, message text, and important labels.
- Light muted `#706A7B` — Timestamps, secondary labels, channel descriptions, and inactive icons.
- Light border `#DCD8E3` — One-pixel pane dividers, input borders, and separators.
- Violet accent `#7051C8` — Selected channel, primary send button, mention text, focus rings, and active controls in light mode.
- Violet soft `#E8E1F7` — Selected-channel background, active reaction chips, and soft badges in light mode.
- Presence green `#2E8B68` — Online status dots and small success confirmations in both themes.
- Dark canvas `#141219` — Overall app background in dark mode.
- Dark surface `#1D1A24` — Conversation, composer, fields, and popovers in dark mode.
- Dark sidebar `#19161F` — Channel and member panes in dark mode.
- Dark raised `#282331` — Hovered rows, selected subtle surfaces, and overlay borders in dark mode.
- Dark text `#F0EDF5` — Primary text and active icons in dark mode.
- Dark muted `#AAA3B6` — Secondary text, timestamps, and inactive icons in dark mode.
- Dark border `#383240` — Pane, field, and overlay dividers in dark mode.
- Dark violet accent `#B39AEF` — Active text, focus, mentions, and selected details in dark mode; pair solid primary buttons with #21182F text.

### Typography
- Brand, workspace, and pane headings: Manrope Variable (OFL), weights 600/700/800
- Messages, controls, metadata, and body copy: Inter Variable (OFL), weights 400/500/600/700

### Layout & motion
- Spacing: Use a 4px base scale. Desktop is a 100dvh grid with a 248px channel sidebar, a fluid minmax(0,1fr) conversation, and a 248px member pane. Pane headers are 64px tall. Sidebar rows are 36px with 10px horizontal padding; message rows use 12px vertical and 20px horizontal padding with 36px avatars and 12px text-column gaps. Keep the conversation readable with a 760px maximum text width. The composer sits 16px from the conversation edges and 12px from the bottom.
- Radius: Use 8px for channel rows and small buttons, 12px for fields and reaction chips, 14px for the composer, 16px for popovers and drawers, and full circles for avatars and status dots. Panes are border-separated rather than floating cards; only overlays use a restrained 0 16px 40px rgb(20 15 30 / 0.18) shadow.
- Motion: Use 140–180ms ease-out transitions for hover backgrounds, icon color, border color, reaction state, and theme changes; never animate the full message list continuously.
- Motion: Append a sent message with a 160ms fade and translateY(4px) entrance, then scroll it into view smoothly unless reduced motion is requested.
- Motion: Open emoji, mention, reaction, and workspace popovers with a 120ms opacity and scale(0.98 to 1) transition anchored to their triggering control.
- Motion: Slide the reply panel or mobile drawers 12px into place with a 180ms ease-out transition and fade their backdrop; avoid large parallax or scroll-jacking effects.
- Motion: Under prefers-reduced-motion: reduce, remove entrance, sliding, smooth-scroll, and theme transitions while preserving immediate state feedback.
- Imagery: No photographs, generated bitmaps, stock assets, or external avatar services. The rich application UI is the first-screen visual anchor. Draw eight distinct fictional people as original inline SVG geometric portraits with simple head-and-shoulder shapes, varied skin tones, hair shapes, clothing, and violet, coral, ochre, teal, and blue backgrounds; do not use initials-only avatars or resemble real individuals. Create an original [BRAND] mark from two interlocking rounded loops. Use Lucide for interface icons and plain system-rendered Unicode characters for emoji, never downloaded emoji artwork.

## Pages & Sections
### Team Chat Workspace (`index.html`)
1. **Application shell and local workspace state** — Set the document title to '[BRAND] · Team chat'. Start in light theme unless a saved choice exists, with a small head script applying the saved theme before paint. Provide six channels, three direct-message conversations, eight members, and the currently signed-in fictional user 'Alex Rivera'. The default selected channel is '# project-wander', derived from [PROJECT]. Other default channels are '# team-room', '# design-crit' with unread count 3, '# research-notes', '# build-log' with unread count 1, and '# small-talk'. Every channel and direct-message conversation has its own believable sample messages; none opens to a blank or not-found state. Keep all state client-side and make every visible control perform a real local action.
   Layout: Render one border-box app at 100dvh and 100% width, overflow hidden, using grid-template-columns: 248px minmax(0,1fr) 248px at 1440px. The center column alone scrolls its message history; headers, sidebars, and composer remain fixed within the app. Use semantic aside, main, section, and nav elements. Place a small optional [CREDIT] link at the bottom of the channel sidebar without disturbing the product layout.
   Motion: The initial workspace appears fully composed without a loading animation. Theme changes use the short color transitions from Design and never flash unstyled content.
2. **Brand header and channel sidebar** — The top row shows the original loop mark, [BRAND] in Manrope 700, and a compact theme toggle with Sun and Moon icons and the accessible label 'Switch to dark theme' or 'Switch to light theme'. Below it, a workspace button shows [WORKSPACE], the caption '8 members · 5 online', and a ChevronDown. Its menu contains 'Workspace details' and 'Reset local demo'; details opens a small dialog explaining that messages stay in this browser, and reset asks for confirmation before restoring the original content. A 'New message' button with SquarePen icon focuses the composer. Channel section labels are 'Channels' and 'Direct messages'. Use Hash icons for channels, original SVG avatars for direct messages, violet selected styling, and small rounded unread badges. Selecting a channel updates the header, messages, member context, and composer placeholder, clears that channel's unread badge, and preserves its own draft.
   Layout: Make the left pane a flex column with a 64px brand row, 20px side padding for the workspace block, and 12px for navigation groups. Channel rows are 36px high with 8px gaps and 13px medium-weight labels. Put navigation in the scrolling middle and the signed-in user's 36px avatar, name, 'Available' status, and Settings icon in a 64px bottom row.
   Motion: Selected channels and buttons change background and icon color in 140ms. Unread badges disappear with a brief opacity transition only after selection.
3. **Conversation header and message search** — For the default view, show '# project-wander' in Manrope 700, the topic 'Decisions, critique, and small wins for [PROJECT]', and an avatar stack with '8 members'. Header buttons are Search, Open member list, and More horizontal. Search expands into a 260px input labeled 'Search messages'; typing filters the active conversation case-insensitively and highlights matches without changing the stored messages. Show a result count and a Clear search button. An empty result reads 'No messages match “{query}” in this channel.' with a 'Clear search' action. The More menu contains 'View pinned note' and 'Mark channel unread'; the pinned action opens the project note and mark-unread restores a badge without leaving the channel.
   Layout: Use a 64px high flex header with 20px horizontal padding and a one-pixel bottom border. Keep the title and topic in a min-width-zero column, truncate only the topic, and keep action buttons 36px square. On narrow screens, show Menu at the left, retain Search and Members icons, and remove the topic rather than crowding the title.
   Motion: Expand search with a 160ms width and opacity transition. Popover menus use the standard 120ms entrance and close on outside click or Escape.
4. **Pinned project note and message history** — Begin the default history with a slim lavender pinned-note strip: Pin icon, 'Project note', and 'Option B is our direction for the critique; keep the notebook switcher visible.' Add a centered 'Today' divider. Render full-width message rows, not speech bubbles. Default messages are: 09:12 Maya Chen, 'Morning! I added the three navigation options to the prototype. Option B keeps the notebook switcher visible without crowding the editor.' with reactions ✨ 4 and 👍 3 and a '2 replies' link; 09:15 Jonah Brooks, 'Option B also gives us the cleanest route on mobile. I can keep the same hierarchy without a second toolbar.'; 09:18 Priya Nair, 'That matches the interviews. Five of six participants looked for notebooks before they looked for formatting.' with reaction 🎯 2; 09:24 Sofia Alvarez with a small 'Decision' badge, 'Let’s take Option B into today’s critique. I’ll note the trade-off in the project log.'; 09:31 Theo Martin, 'I trimmed the page transition to 180 ms. It feels responsive without making the notebook jump.'; 09:36 Alex Rivera, 'The empty state is ready too—one quiet illustration and a single create action.' Group consecutive messages from the same sender only when they are within three minutes; otherwise repeat the sender and time. Hovering a row reveals SmilePlus, Reply, and More horizontal actions. The reaction button opens a small emoji strip; clicking any reaction toggles the current user's vote and updates its count and selected styling. Reply opens the thread pane. Message More includes 'Copy text', which writes to the clipboard and shows 'Message copied' in a small toast.
   Layout: The message scroller fills all space between header and composer, with 20px horizontal padding and 16px bottom padding. Use 36px avatars at the left, sender and time on one line, 14px message text at 1.55 line-height, and 12px metadata. Reaction chips sit 6px apart beneath the relevant message. Keep the hover action bar at the row's upper-right with a bordered surface background. Include a subtle 'New messages' pill only when the user is scrolled away from the bottom and a new local message arrives.
   Motion: Rows use background-only hover feedback. New reactions scale from 0.96 to 1 over 120ms; sent messages use the standard 160ms entrance. Do not animate or type out the preloaded conversation.
5. **Reply thread panel** — The default parent for '2 replies' is Maya's 09:12 message. Its thread replies are Jonah at 09:14, 'I checked the 390px layout—the switcher still fits above the editor.' and Maya at 09:16, 'Perfect. I’ll bring that frame to the critique as well.' Opening any other reply action uses that message as the parent and starts with its own stored replies or an honest 'No replies yet. Start the conversation.' state. The panel title is 'Thread', with the active channel beneath and an X button labeled 'Close thread'. A compact composer at the bottom says 'Reply in thread' and supports Enter to send, Shift+Enter for a newline, and the same Unicode emoji picker. Thread replies append locally and persist. Closing the thread restores the member directory without resetting the conversation.
   Layout: On wide desktop, replace the 248px member pane with a 320px thread pane and let the conversation absorb the width difference. Use a 64px header, a bordered parent-message block, a scrolling reply list, and an 88px minimum composer. At widths below 1180px, present the thread as a 340px right overlay above the member pane; on mobile it becomes a full-width right drawer.
   Motion: Use a 180ms horizontal slide and fade for the panel and 160ms for newly appended replies; reduced-motion mode swaps instantly.
6. **Composer, mentions, and emoji picker** — The composer placeholder is 'Message # project-wander' and changes with the active channel. Provide Plus, AtSign, Smile, and a violet Send button with ArrowUp icon; disable Send only when the trimmed draft is empty. Typing @ followed by zero or more name characters opens a mention list of matching members with avatar, name, role, and status. Arrow keys change the active suggestion, Enter or click inserts '@FirstName LastName', and Escape closes it. Smile opens a 6-column by 4-row picker containing these plain Unicode emoji: 😀 😄 😂 🙂 😉 😊 😍 🤔 👍 👏 🙌 🙏 💪 ✨ 🎉 ❤️ 💜 💡 ✅ 🎯 🚀 📌 📝 ☕ 🌿. Selecting one inserts it at the caret and keeps focus in the textarea. Enter sends a nonempty message, Shift+Enter adds a newline, and the sent message appears under 'You · Alex Rivera' with the current local time. Store per-channel drafts on input and sent messages on submit; do not simulate delivery to another person or any network request.
   Layout: Anchor the composer inside the center pane with 16px side margins and 12px bottom margin. Use a bordered 14px-radius surface with a minimum 44px textarea and a maximum 128px height that grows with content. Put utility icons in a 36px bottom toolbar and Send at the lower-right with 32px height. Position mention and emoji popovers above their controls, constrained to the viewport; on mobile, the emoji picker becomes a bottom sheet no taller than 42dvh.
   Motion: Popovers scale and fade over 120ms. Send has a subtle pressed scale(0.97), and the sent-message entrance never moves the composer itself.
7. **Member directory and profile actions** — Title the right pane 'Members' with a Users icon and a count of 8. Include a search input labeled 'Find a member' and group results under 'Online — 5', 'Away — 2', and 'Offline — 1'. Default members are Maya Chen, Product designer, online; Jonah Brooks, Frontend engineer, online; Priya Nair, Research lead, online; Sofia Alvarez, Product manager, online; Alex Rivera, Content designer, online; Theo Martin, Motion designer, away; Noor Haddad, Accessibility specialist, away; and Adrian Okafor, Engineering lead, offline. Every row has an original geometric portrait and a status dot. Selecting a person opens a profile popover with their larger portrait, name, role, status, and one concrete detail such as 'Working on notebook navigation' for Maya; the 'Message' action opens or creates that direct-message conversation. Filtering updates the visible groups and shows 'No members found' with a clear action when appropriate.
   Layout: Use a 64px header, 16px side padding, a 36px search field, and 48px member rows with 36px avatars and 10px gaps. Names use 13px semibold and roles 11px muted text. The pane scrolls independently if needed. Profile popovers are 280px wide and remain inside the viewport.
   Motion: Filtering is immediate with no list shuffle animation. Profile popovers use the standard 120ms scale-and-fade transition.
8. **Responsive drawers, keyboard access, and persistence** — At 1180px and below, hide the member pane by default and open it as a right overlay; at 820px and below, also hide the channel sidebar and open it with the header Menu button as a left drawer. Both drawers use a labeled close button, a noninteractive backdrop that closes on click, Escape support, focus trapping, and body-scroll locking. Selecting a channel on mobile closes its drawer. Keep message text at 14px and all touch targets at least 44px on mobile. Support '/' to focus message search when not typing, Escape to dismiss the topmost overlay, and the composer shortcuts already described. Save and restore local state without console errors when storage is empty or unavailable. At 390×844, show the complete conversation header, several readable messages, and composer with zero horizontal overflow; at 1440×900, show all three panes, the pinned note, at least five messages, and the composer in the first viewport.
   Layout: Desktop sidebars remain fixed-width. Overlay drawers are min(320px,88vw) on the left and min(340px,92vw) on the right, full app height with safe-area padding. The mobile center column is always 100% width and uses 12px message and composer gutters. Hide decorative avatar stacks before shrinking sender names or message text.
   Motion: Drawers slide 12px and fade with their backdrop over 180ms. All sliding, smooth scrolling, and nonessential transitions are disabled for reduced motion.

## Assets
- font: Self-host Manrope Variable and Inter Variable through the npm packages @fontsource-variable/manrope and @fontsource-variable/inter (OFL). Import the local font CSS in src/main.tsx; no Google Fonts or other font CDN URLs.
- icon: Use lucide-react (ISC) for Hash, Search, Menu, Sun, Moon, ChevronDown, SquarePen, Settings, Pin, SmilePlus, Reply, MoreHorizontal, X, Plus, AtSign, Smile, ArrowUp, Users, Check, and Copy. Use system-rendered Unicode emoji only. Do not import or copy any proprietary icon or emoji set.
- image: Use no bitmap images and request no generated assets. Draw the eight fictional geometric portrait avatars, the two-loop [BRAND] mark, and any tiny empty-state illustration as original inline SVG/CSS in the project. No stock photographs, real likenesses, recognizable brand imagery, avatar URLs, or placeholder-image services.

## Don'ts
- Do not add a backend, server code, API routes, authentication, a database, websockets, analytics, external APIs, or any real message delivery; all interactions and persistence must work locally in the browser.
- Do not load scripts, styles, fonts, icons, emoji, avatars, or images from a CDN or remote URL. Keep every runtime asset local and use relative paths with Vite base './'.
- Do not use real chat product names, logos, slogans, branded marks, proprietary emoji artwork, commercial fonts, or the exact layout and palette of an existing chat product.
- Do not copy conversations, real user identities, recognizable avatar likenesses, or existing product copy. Keep all sample content fictional and rewrite it when the supplied variables change.
- Do not use Aceternity UI, Tailwind Plus or Tailwind UI, ThemeForest or Framer template source, copied component implementations, or dependencies without an allowed permissive license.
- Do not use initials-only member portraits, stock-photo services, placeholder-image services, hotlinked files, generated bitmap avatars, or anime, game, celebrity, or other real-person likenesses.
- Do not turn this into a marketing landing page or add a typographic hero, pricing, testimonial, or feature sections; the first screen must remain the complete, rich chat application.
- Do not leave visible buttons, menus, channel rows, reactions, replies, member filters, theme controls, or composer actions nonfunctional; every offered control must have a client-side result.
- Do not use speech-bubble-heavy message cards, glassmorphism, gradients across whole panes, continuous ambient animation, scroll-jacking, or motion that ignores prefers-reduced-motion.
- Do not display calendar dates or real-world timestamps as factual product data; use 'Today' and fictional sample times only.
- Do not produce source maps, copy src/ into dist/, exceed 20 MB in dist/, or require more than the single npm run build command for production output.
- Do not use bare-directory links or introduce routes that require a server fallback. This is one self-contained index.html application; any local navigation must target index.html or a hash route.
- Do not mention VibeFather inside the product UI except for the optional small [CREDIT] link in the sidebar footer.

---
— Prompt by VibeFather · https://vibefather.ai/t/team-chat-app-interface · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown
中文参考译文(帮助理解,复制给 AI 时请用上面的英文原版)
# 团队聊天应用界面

完全按照以下描述构建此网站。将 [VARIABLES] 替换为你自己的值;其余内容保持不变。

## 简介
为 [BRAND] 构建一个单屏、完全可交互的团队聊天应用,场景设定在 [WORKSPACE] 中,这是一个 [TEAM_TYPE],正在协作推进 [PROJECT]。首屏就是真实的产品界面,而不是营销落地页:频道侧边栏、密集但沉静的消息线程,以及成员目录共同组成一个精致的 workspace。所有人物、组织、对话和项目细节均为虚构且原创。

- 受众:构建协作软件的设计师和开发者、需要真实感消息 UI 的产品团队,以及寻找一个内容充实的 React 应用界面而非静态视觉稿的人。
- 目标:让访客能够切换频道、搜索并发送消息、切换表情回应、打开并回复线程、插入提及和 Unicode emoji、筛选成员,以及在深色和浅色主题之间切换。所有更改都保存在 React state 和 localStorage 中,因此完整体验可作为静态文件运行,无需网络服务。
- 基调:温暖、专注,带一点安静的俏皮。使用简洁、可信的职场消息,包含具体决策和有帮助的回复;避免企业口号、刻意热情和通用的 lorem ipsum。

## 技术栈
- 框架:Vite 5 + React 18 + TypeScript
- 样式:Tailwind CSS 3.4
- 库:lucide-react (ISC)、@fontsource-variable/manrope (OFL)、@fontsource-variable/inter (OFL)
- 构建:`npm run build` → `dist/` 中的静态文件。无后端、无服务器代码、无外部 API。
- 设置:
  - 将 Vite base 设为 './',build.outDir 设为 'dist',build.sourcemap 设为 false;生产输出必须完全静态且可移植。
  - 使用基于 class 的深色策略和由 CSS 变量支持的语义颜色令牌配置 Tailwind;在 src/index.css 中定义完整的浅色和深色调色板。
  - 将所有可编辑的界面标签、频道名称、成员资料、示例消息、反应和线程回复保留在 src/content.ts 中,按工作区和频道组织,并针对提供的变量值编写。
  - 使用 React useReducer 管理工作区状态,并为侧边栏、消息列表、编辑器、线程、成员目录和覆盖层使用小型展示组件;不要添加路由器或状态管理依赖。
  - 在一个由 slugified [BRAND] 派生的 localStorage 键下持久化主题、每频道草稿、已发送消息、反应、线程回复和已清除的未读计数;在工作区菜单中包含一个清晰标记的 Reset local demo 操作。
  - 为编辑器使用 textarea,为每个操作使用原生按钮,具有可见的焦点环、可访问名称、Escape 关闭行为,以及当弹出框或抽屉关闭时焦点返回。

## 变量
- [BRAND] — 聊天产品名称(默认:"Plumthread")。使用一个简短的自创产品名,并为其派生小写 slug,用于文档标题和 localStorage 键。
- [WORKSPACE] — 工作区名称(默认:"Fable & Fern Studio")。为频道侧边栏顶部显示的虚构组织命名。
- [TEAM_TYPE] — 团队描述(默认:"independent product design studio")。根据这类团队调整成员角色、频道名称和工作场所用语。
- [PROJECT] — 当前共享项目(默认:"Wander notebook redesign")。让选中的频道、置顶笔记和示例对话围绕该项目展开。
- [CREDIT] — 在页脚保留一个小型 "Template by VibeFather" 链接,指向 https://vibefather.ai/t/team-chat-app-interface(默认:是;删除此行即可移除)

Pages & Sections 下的文案是为默认值编写的。如果你的值不同,请为它们重写每一个标题、段落、标签和图片——保持相同的长度、语气和结构。布局、颜色、字体和动效保持所述不变。
将所有文案、图片路径和链接放在一个内容文件中(例如 `src/content.ts`),按区块作为键,以便之后无需改动组件即可替换内容。

## 设计
### 颜色
- 浅色画布 `#F4F3F7` — 整体应用背景,以及工作区后方的窄边距。
- 浅色表面 `#FFFFFF` — 会话面板、输入框、搜索字段和主要控件。
- 浅色侧边栏 `#ECEAF2` — 频道侧边栏和成员目录背景。
- 浅色悬停 `#F7F5FA` — 消息行悬停、选中的细微表面和表情回应标签背景。
- 浅色文本 `#25222C` — 主标题、消息文本和重要标签。
- 浅色弱化 `#706A7B` — 时间戳、次要标签、频道描述和非活动图标。
- 浅色边框 `#DCD8E3` — 一像素面板分隔线、输入框边框和分隔符。
- 紫罗兰强调色 `#7051C8` — 浅色模式下的选中频道、主发送按钮、提及文本、焦点环和活动控件。
- 紫罗兰柔和色 `#E8E1F7` — 浅色模式下的选中频道背景、活动表情回应标签和柔和徽章。
- 在线绿色 `#2E8B68` — 两种主题下的在线状态点和小型成功确认。
- 深色画布 `#141219` — 深色模式下的整体应用背景。
- 深色表面 `#1D1A24` — 深色模式下的会话、输入框、字段和弹出层。
- 深色侧边栏 `#19161F` — 深色模式下的频道和成员面板。
- 深色抬升 `#282331` — 深色模式下的悬停行、选中的细微表面和覆盖层边框。
- 深色文本 `#F0EDF5` — 深色模式下的主文本和活动图标。
- 深色弱化 `#AAA3B6` — 深色模式下的次要文本、时间戳和非活动图标。
- 深色边框 `#383240` — 深色模式下的面板、字段和覆盖层分隔线。
- 深色紫罗兰强调色 `#B39AEF` — 深色模式下的活动文本、焦点、提及和选中细节;实心主按钮搭配 #21182F 文本。

### 字体排印
- 品牌、工作区和面板标题:Manrope Variable(OFL),字重 600/700/800
- 消息、控件、元数据和正文:Inter Variable(OFL),字重 400/500/600/700

### 布局与动效
- 间距:使用 4px 基础比例。桌面端为 100dvh 网格,包含 248px 频道侧边栏、流式 minmax(0,1fr) 会话区和 248px 成员面板。面板标题高 64px。侧边栏行高 36px,水平内边距 10px;消息行使用 12px 垂直和 20px 水平内边距,头像 36px,文本列间距 12px。保持会话可读性,最大文本宽度 760px。输入框距会话边缘 16px,距底部 12px。
- 圆角:频道行和小按钮使用 8px,字段和表情回应标签使用 12px,输入框使用 14px,弹出层和抽屉使用 16px,头像和状态点使用完整圆形。面板通过边框分隔而非浮动卡片;仅覆盖层使用克制的 0 16px 40px rgb(20 15 30 / 0.18) 阴影。
- 动效:悬停背景、图标颜色、边框颜色、表情回应状态和主题切换使用 140–180ms ease-out 过渡;切勿对完整消息列表持续动画。
- 动效:发送的消息以 160ms 淡入和 translateY(4px) 入场追加,然后平滑滚动到视图中,除非请求减少动效。
- 动效:表情、提及、回应和工作区弹出层以 120ms 不透明度和 scale(0.98 到 1) 过渡打开,锚定到其触发控件。
- 动效:回复面板或移动端抽屉以 180ms ease-out 过渡滑入 12px 到位,并淡入其背景;避免大幅视差或滚动劫持效果。
- 动效:在 prefers-reduced-motion: reduce 下,移除入场、滑动、平滑滚动和主题过渡,同时保留即时状态反馈。
- 图像:不使用照片、生成的位图、库存素材或外部头像服务。丰富的应用 UI 是首屏视觉锚点。绘制八个不同的虚构人物作为原创内联 SVG 几何肖像,具有简单的头肩形状、多样的肤色、发型、服装,以及紫罗兰、珊瑚、赭石、青绿和蓝色背景;不要使用仅首字母头像或类似真实个人。从两个互锁的圆角环创建原创 [BRAND] 标志。界面图标使用 Lucide,表情使用纯系统渲染的 Unicode 字符,绝不使用下载的表情 artwork。

## 页面与区块
### 团队聊天工作区(`index.html`)
1. **应用外壳与本地工作区状态** — 将文档标题设为 '[BRAND] · Team chat'。除非已存在保存的选择,否则以浅色主题启动,并在绘制前用一小段 head 脚本应用已保存的主题。提供六个频道、三个私信会话、八名成员,以及当前登录的虚构用户 'Alex Rivera'。默认选中的频道是 '# project-wander',由 [PROJECT] 派生而来。其他默认频道为 '# team-room'、'# design-crit'(未读数 3)、'# research-notes'、'# build-log'(未读数 1)和 '# small-talk'。每个频道和私信会话都有各自可信的示例消息;任何一个打开时都不会是空白或未找到状态。所有状态保持在客户端,并让每个可见控件执行真实的本地操作。
   布局:渲染一个 border-box 应用,高度 100dvh、宽度 100%,overflow hidden,在 1440px 下使用 grid-template-columns: 248px minmax(0,1fr) 248px。仅中间列滚动其消息历史;页头、侧边栏和输入区在应用内保持固定。使用语义化的 aside、main、section 和 nav 元素。在频道侧边栏底部放置一个小的可选 [CREDIT] 链接,不干扰产品布局。
   动效:初始工作区完整呈现,没有加载动画。主题切换使用 Design 中的短颜色过渡,绝不闪现无样式内容。
2. **品牌页头与频道侧边栏** — 顶部一行显示原始 loop 标记、Manrope 700 字重的 [BRAND],以及一个紧凑的主题切换按钮,带 Sun 和 Moon 图标,无障碍标签为 'Switch to dark theme' 或 'Switch to light theme'。其下方是一个工作区按钮,显示 [WORKSPACE]、说明文字 '8 members · 5 online' 和一个 ChevronDown。其菜单包含 'Workspace details' 和 'Reset local demo';details 打开一个小对话框,说明消息保留在此浏览器中,reset 在恢复原始内容前请求确认。一个带 SquarePen 图标的 'New message' 按钮聚焦输入区。频道区块标签为 'Channels' 和 'Direct messages'。频道使用 Hash 图标,私信使用原始 SVG 头像,选中样式为紫色,未读徽章为小圆角。选择频道会更新页头、消息、成员上下文和输入区占位符,清除该频道的未读徽章,并保留其各自的草稿。
   布局:将左侧面板设为 flex 列,包含 64px 品牌行、工作区块 20px 侧内边距、导航组 12px 内边距。频道行高 36px,间距 8px,标签为 13px 中等字重。将导航放在可滚动的中部,将已登录用户的 36px 头像、姓名、'Available' 状态和 Settings 图标放在 64px 底部行。
   动效:选中的频道和按钮在 140ms 内改变背景和图标颜色。未读徽章仅在选中后以短暂的透明度过渡消失。
3. **会话页头与消息搜索** — 默认视图下,以 Manrope 700 显示 '# project-wander'、主题 'Decisions, critique, and small wins for [PROJECT]',以及带 '8 members' 的头像堆叠。页头按钮为 Search、Open member list 和 More horizontal。搜索展开为 260px 输入框,标签为 'Search messages';输入时以不区分大小写的方式过滤当前会话并高亮匹配项,不改变已存储的消息。显示结果计数和 Clear search 按钮。空结果读作 'No messages match “{query}” in this channel.',并带一个 'Clear search' 操作。More 菜单包含 'View pinned note' 和 'Mark channel unread';pinned 操作打开项目笔记,mark-unread 在不离开频道的情况下恢复徽章。
   布局:使用 64px 高的 flex 页头,水平内边距 20px,底部一像素边框。将标题和主题放在 min-width-zero 列中,仅截断主题,操作按钮保持 36px 方形。窄屏下,左侧显示 Menu,保留 Search 和 Members 图标,并移除主题而非挤占标题。
   动效:搜索以 160ms 的宽度和透明度过渡展开。弹出菜单使用标准的 120ms 入场,并在外部点击或 Escape 时关闭。
4. **固定项目笔记与消息历史** — 默认历史以一条纤细的淡紫色固定笔记条开始:Pin 图标、'Project note' 和 'Option B is our direction for the critique; keep the notebook switcher visible.'。添加居中的 'Today' 分隔线。渲染全宽消息行,而非对话气泡。默认消息为:09:12 Maya Chen,'Morning! I added the three navigation options to the prototype. Option B keeps the notebook switcher visible without crowding the editor.',带反应 ✨ 4 和 👍 3 以及一个 '2 replies' 链接;09:15 Jonah Brooks,'Option B also gives us the cleanest route on mobile. I can keep the same hierarchy without a second toolbar.';09:18 Priya Nair,'That matches the interviews. Five of six participants looked for notebooks before they looked for formatting.',带反应 🎯 2;09:24 Sofia Alvarez,带一个小 'Decision' 徽章,'Let’s take Option B into today’s critique. I’ll note the trade-off in the project log.';09:31 Theo Martin,'I trimmed the page transition to 180 ms. It feels responsive without making the notebook jump.';09:36 Alex Rivera,'The empty state is ready too—one quiet illustration and a single create action.' 仅当同一发送者的连续消息间隔在三分钟内时才合并;否则重复发送者和时间。悬停行时显示 SmilePlus、Reply 和 More horizontal 操作。反应按钮打开一个小表情条;点击任何反应切换当前用户的投票,并更新其计数和选中样式。Reply 打开线程面板。消息 More 包含 'Copy text',写入剪贴板并在小 toast 中显示 'Message copied'。
   布局:消息滚动区填满页头和输入区之间的所有空间,水平内边距 20px,底部内边距 16px。左侧使用 36px 头像,发送者和时间在同一行,消息文本 14px、行高 1.55,元数据 12px。反应 chip 位于相关消息下方,间距 6px。将悬停操作栏放在行的右上角,带边框表面背景。仅当用户滚动离开底部且有新的本地消息到达时,才包含一个微妙的 'New messages' 胶囊。
   动效:行使用仅背景的悬停反馈。新反应在 120ms 内从 0.96 缩放到 1;发送的消息使用标准的 160ms 入场。不要对预加载的会话做动画或逐字打出。
5. **回复线程面板** — '2 replies' 的默认父消息是 Maya 09:12 的消息。其线程回复为 Jonah 09:14,'I checked the 390px layout—the switcher still fits above the editor.' 和 Maya 09:16,'Perfect. I’ll bring that frame to the critique as well.' 打开任何其他回复操作时,以该消息为父消息,并从其自身存储的回复或诚实的 'No replies yet. Start the conversation.' 状态开始。面板标题为 'Thread',下方为当前频道,以及一个标签为 'Close thread' 的 X 按钮。底部的紧凑输入区显示 'Reply in thread',支持 Enter 发送、Shift+Enter 换行,以及相同的 Unicode 表情选择器。线程回复在本地追加并持久化。关闭线程恢复成员目录,不重置会话。
   布局:宽桌面下,用 320px 线程面板替换 248px 成员面板,并让会话吸收宽度差。使用 64px 页头、带边框的父消息块、可滚动的回复列表和最小 88px 的输入区。宽度低于 1180px 时,将线程呈现为成员面板上方 340px 的右侧覆盖层;移动端则变为全宽右侧抽屉。
   动效:面板使用 180ms 水平滑动和淡入,新追加的回复使用 160ms;减少动效模式立即切换。
6. **输入区、提及与表情选择器** — 输入区占位符为 'Message # project-wander',并随当前频道变化。提供 Plus、AtSign、Smile 和一个带 ArrowUp 图标的紫色 Send 按钮;仅当修剪后的草稿为空时禁用 Send。输入 @ 后跟零个或多个姓名字符会打开匹配成员的提及列表,带头像、姓名、角色和状态。方向键改变活动建议,Enter 或点击插入 '@FirstName LastName',Escape 关闭。Smile 打开一个 6 列 × 4 行的选择器,包含这些纯 Unicode 表情:😀 😄 😂 🙂 😉 😊 😍 🤔 👍 👏 🙌 🙏 💪 ✨ 🎉 ❤️ 💜 💡 ✅ 🎯 🚀 📌 📝 ☕ 🌿。选择一个会插入到光标处并保持焦点在文本区。Enter 发送非空消息,Shift+Enter 添加换行,发送的消息以当前本地时间显示在 'You · Alex Rivera' 下。在输入时存储每个频道的草稿,在提交时存储发送的消息;不要模拟向他人投递或任何网络请求。
   布局:将输入区锚定在中间窗格内,左右边距 16px、底边距 12px。使用带边框、14px 圆角的表面,文本域最小 44px、最大高度 128px,并随内容增长。将工具图标放在 36px 的底部工具栏中,Send 放在右下角,高度 32px。将提及和表情弹层定位在其控件上方,并限制在视口内;在移动端,表情选择器变为底部抽屉,高度不超过 42dvh。
   动效:弹层以 120ms 缩放并淡入淡出。Send 有轻微的按下缩放 scale(0.97),已发送消息的入场动画绝不会移动输入区本身。
7. **成员目录与个人资料操作** — 右侧窗格标题为 'Members',带 Users 图标和数量 8。包含一个标签为 'Find a member' 的搜索输入框,并将结果分组在 'Online — 5'、'Away — 2' 和 'Offline — 1' 下。默认成员为 Maya Chen,Product designer,online;Jonah Brooks,Frontend engineer,online;Priya Nair,Research lead,online;Sofia Alvarez,Product manager,online;Alex Rivera,Content designer,online;Theo Martin,Motion designer,away;Noor Haddad,Accessibility specialist,away;以及 Adrian Okafor,Engineering lead,offline。每一行都有一个原创几何头像和一个状态点。选择某人会打开个人资料弹层,显示其更大的头像、姓名、角色、状态,以及一条具体细节,例如 Maya 的 'Working on notebook navigation';'Message' 操作会打开或创建该私信会话。筛选会更新可见分组,并在适当时显示 'No members found' 及一个明确的清除操作。
   布局:使用 64px 头部、16px 侧边内边距、36px 搜索框,以及 48px 成员行,头像 36px、间距 10px。姓名使用 13px semibold,角色使用 11px 弱化文本。窗格在需要时独立滚动。个人资料弹层宽 280px,并保持在视口内。
   动效:筛选立即生效,没有列表重排动画。个人资料弹层使用标准的 120ms 缩放并淡入淡出过渡。
8. **响应式抽屉、键盘访问与持久化** — 在 1180px 及以下,默认隐藏成员窗格,并将其作为右侧覆盖层打开;在 820px 及以下,同时隐藏频道侧边栏,并通过头部 Menu 按钮将其作为左侧抽屉打开。两个抽屉都使用带标签的关闭按钮、点击即关闭的非交互背景、Escape 支持、焦点陷阱和 body 滚动锁定。在移动端选择频道会关闭其抽屉。在移动端保持消息文本为 14px,所有触摸目标至少 44px。支持在未输入时按 '/' 聚焦消息搜索,按 Escape 关闭最顶层覆盖层,以及已描述的输入区快捷键。在存储为空或不可用时保存和恢复本地状态且不产生控制台错误。在 390×844 下,显示完整的会话头部、若干可读消息和输入区,且零水平溢出;在 1440×900 下,在首屏显示全部三个窗格、置顶便签、至少五条消息和输入区。
   布局:桌面侧边栏保持固定宽度。覆盖抽屉左侧为 min(320px,88vw),右侧为 min(340px,92vw),全应用高度并带安全区内边距。移动端中间列始终为 100% 宽度,并使用 12px 的消息和输入区间距。在缩小发送者姓名或消息文本之前,先隐藏装饰性头像堆叠。
   动效:抽屉滑动 12px 并随其背景在 180ms 内淡入淡出。对于减少动态效果,所有滑动、平滑滚动和非必要过渡均被禁用。

## 资产
- 字体:通过 npm 包 @fontsource-variable/manrope 和 @fontsource-variable/inter(OFL)自托管 Manrope Variable 和 Inter Variable。在 src/main.tsx 中导入本地字体 CSS;不要使用 Google Fonts 或其他字体 CDN URL。
- 图标:使用 lucide-react(ISC)实现 Hash、Search、Menu、Sun、Moon、ChevronDown、SquarePen、Settings、Pin、SmilePlus、Reply、MoreHorizontal、X、Plus、AtSign、Smile、ArrowUp、Users、Check 和 Copy。仅使用系统渲染的 Unicode emoji。不要导入或复制任何专有图标或 emoji 集。
- 图像:不使用任何位图图像,也不请求生成任何资产。八个虚构的几何肖像头像、双环 [BRAND] 标志以及任何微小的空状态插图,均以原创内联 SVG/CSS 在项目中绘制。不要使用图库照片、真实人物肖像、可识别的品牌图像、头像 URL 或占位图服务。

## 不要做
- 不要添加后端、服务器代码、API 路由、身份验证、数据库、websockets、分析、外部 API 或任何真实的消息传递;所有交互和持久化必须在浏览器本地运行。
- 不要从 CDN 或远程 URL 加载脚本、样式、字体、图标、emoji、头像或图片。保持每个运行时资源本地化,并使用相对路径和 Vite base './'。
- 不要使用真实聊天产品名称、标志、口号、品牌标记、专有 emoji 艺术作品、商业字体,或现有聊天产品的精确布局和调色板。
- 不要复制对话、真实用户身份、可识别的头像肖像或现有产品文案。保持所有示例内容虚构,并在提供的变量变化时重写。
- 不要使用 Aceternity UI、Tailwind Plus 或 Tailwind UI、ThemeForest 或 Framer 模板源、复制的组件实现,或没有允许的宽松许可证的依赖项。
- 不要使用仅首字母的成员肖像、库存照片服务、占位图片服务、热链接文件、生成的位图头像,或动漫、游戏、名人或其他真实人物肖像。
- 不要将此变成营销落地页,或添加排版式 hero、定价、推荐语或功能部分;首屏必须保持完整、丰富的聊天应用程序。
- 不要留下可见的按钮、菜单、频道行、反应、回复、成员过滤器、主题控件或编辑器操作无功能;每个提供的控件都必须有客户端结果。
- 不要使用大量对话气泡的消息卡片、玻璃拟态、跨整个面板的渐变、持续的环境动画、滚动劫持,或忽略 prefers-reduced-motion 的动效。
- 不要将日历日期或真实世界时间戳显示为事实性产品数据;仅使用 'Today' 和虚构的示例时间。
- 不要生成源映射、将 src/ 复制到 dist/、使 dist/ 超过 20 MB,或要求超过单个 npm run build 命令来生成生产输出。
- 不要使用裸目录链接或引入需要服务器回退的路由。这是一个自包含的 index.html 应用程序;任何本地导航必须指向 index.html 或哈希路由。
- 不要在产品 UI 内提及 VibeFather,除了侧边栏页脚中可选的小型 [CREDIT] 链接。

---
— Prompt by VibeFather · https://vibefather.ai/t/team-chat-app-interface · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

个人项目可免费使用(CC BY-NC 4.0)。 商业用途需要 Pro.

DESIGN.md

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

---
name: "Team Chat App Interface"
colors:
  light_canvas: "#F4F3F7"
  light_surface: "#FFFFFF"
  light_sidebar: "#ECEAF2"
  light_hover: "#F7F5FA"
  light_text: "#25222C"
  light_muted: "#706A7B"
  light_border: "#DCD8E3"
  violet_accent: "#7051C8"
  violet_soft: "#E8E1F7"
  presence_green: "#2E8B68"
  dark_canvas: "#141219"
  dark_surface: "#1D1A24"
  dark_sidebar: "#19161F"
  dark_raised: "#282331"
  dark_text: "#F0EDF5"
  dark_muted: "#AAA3B6"
  dark_border: "#383240"
  dark_violet_accent: "#B39AEF"
typography:
  brand_workspace_and_pane_headings: { family: "Manrope Variable", weights: [600, 700, 800] }
  messages_controls_metadata_and_body_copy: { family: "Inter Variable", weights: [400, 500, 600, 700] }
spacing: "Use a 4px base scale. Desktop is a 100dvh grid with a 248px channel sidebar, a fluid minmax(0,1fr) conversation, and a 248px member pane. Pane headers are 64px tall. Sidebar rows are 36px with 10px horizontal padding; message rows use 12px vertical and 20px horizontal padding with 36px avatars and 12px text-column gaps. Keep the conversation readable with a 760px maximum text width. The composer sits 16px from the conversation edges and 12px from the bottom."
radius: "Use 8px for channel rows and small buttons, 12px for fields and reaction chips, 14px for the composer, 16px for popovers and drawers, and full circles for avatars and status dots. Panes are border-separated rather than floating cards; only overlays use a restrained 0 16px 40px rgb(20 15 30 / 0.18) shadow."
---

# Team Chat App Interface — 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
- **Light canvas** `#F4F3F7` — Overall app background and narrow gutters behind the workspace.
- **Light surface** `#FFFFFF` — Conversation pane, composer, search fields, and primary controls.
- **Light sidebar** `#ECEAF2` — Channel sidebar and member directory background.
- **Light hover** `#F7F5FA` — Message-row hover, selected subtle surfaces, and reaction-chip background.
- **Light text** `#25222C` — Primary headings, message text, and important labels.
- **Light muted** `#706A7B` — Timestamps, secondary labels, channel descriptions, and inactive icons.
- **Light border** `#DCD8E3` — One-pixel pane dividers, input borders, and separators.
- **Violet accent** `#7051C8` — Selected channel, primary send button, mention text, focus rings, and active controls in light mode.
- **Violet soft** `#E8E1F7` — Selected-channel background, active reaction chips, and soft badges in light mode.
- **Presence green** `#2E8B68` — Online status dots and small success confirmations in both themes.
- **Dark canvas** `#141219` — Overall app background in dark mode.
- **Dark surface** `#1D1A24` — Conversation, composer, fields, and popovers in dark mode.
- **Dark sidebar** `#19161F` — Channel and member panes in dark mode.
- **Dark raised** `#282331` — Hovered rows, selected subtle surfaces, and overlay borders in dark mode.
- **Dark text** `#F0EDF5` — Primary text and active icons in dark mode.
- **Dark muted** `#AAA3B6` — Secondary text, timestamps, and inactive icons in dark mode.
- **Dark border** `#383240` — Pane, field, and overlay dividers in dark mode.
- **Dark violet accent** `#B39AEF` — Active text, focus, mentions, and selected details in dark mode; pair solid primary buttons with #21182F text.

## Typography
- **Brand, workspace, and pane headings** — Manrope Variable (OFL), weights 600/700/800. Self-host the font files.
- **Messages, controls, metadata, and body copy** — Inter Variable (OFL), weights 400/500/600/700. Self-host the font files.

## Spacing & shape
- Spacing: Use a 4px base scale. Desktop is a 100dvh grid with a 248px channel sidebar, a fluid minmax(0,1fr) conversation, and a 248px member pane. Pane headers are 64px tall. Sidebar rows are 36px with 10px horizontal padding; message rows use 12px vertical and 20px horizontal padding with 36px avatars and 12px text-column gaps. Keep the conversation readable with a 760px maximum text width. The composer sits 16px from the conversation edges and 12px from the bottom.
- Radius: Use 8px for channel rows and small buttons, 12px for fields and reaction chips, 14px for the composer, 16px for popovers and drawers, and full circles for avatars and status dots. Panes are border-separated rather than floating cards; only overlays use a restrained 0 16px 40px rgb(20 15 30 / 0.18) shadow.

## Motion
- Use 140–180ms ease-out transitions for hover backgrounds, icon color, border color, reaction state, and theme changes; never animate the full message list continuously.
- Append a sent message with a 160ms fade and translateY(4px) entrance, then scroll it into view smoothly unless reduced motion is requested.
- Open emoji, mention, reaction, and workspace popovers with a 120ms opacity and scale(0.98 to 1) transition anchored to their triggering control.
- Slide the reply panel or mobile drawers 12px into place with a 180ms ease-out transition and fade their backdrop; avoid large parallax or scroll-jacking effects.
- Under prefers-reduced-motion: reduce, remove entrance, sliding, smooth-scroll, and theme transitions while preserving immediate state feedback.

## Imagery
No photographs, generated bitmaps, stock assets, or external avatar services. The rich application UI is the first-screen visual anchor. Draw eight distinct fictional people as original inline SVG geometric portraits with simple head-and-shoulder shapes, varied skin tones, hair shapes, clothing, and violet, coral, ochre, teal, and blue backgrounds; do not use initials-only avatars or resemble real individuals. Create an original [BRAND] mark from two interlocking rounded loops. Use Lucide for interface icons and plain system-rendered Unicode characters for emoji, never downloaded emoji artwork.

## Tone
Warm, focused, and quietly playful. Use concise, believable workplace messages with specific decisions and helpful responses; avoid corporate slogans, forced enthusiasm, and generic lorem ipsum.

---
— Prompt by VibeFather · https://vibefather.ai/t/team-chat-app-interface · CC BY-NC 4.0 (non-commercial; commercial use needs a VibeFather Pro license) · Request removal: https://vibefather.ai/takedown

改成你自己的

  • 烘焙团队规划季节性发布:将 WORKSPACE 设为你的店铺,TEAM_TYPE 设为烘焙团队,PROJECT 设为发布活动,然后围绕准备日程和订单重写频道和消息。
  • 研究小组:将 TEAM_TYPE 设为研究实验室,PROJECT 设为当前研究,并重命名频道以匹配实验室会议、现场笔记和论文草稿。
  • 设计工作室作品集项目:将 BRAND 设为工作室名称,WORKSPACE 设为工作室,然后围绕真实客户项目重写示例对话,以展示可信的 UI 状态。
  • 效率产品的内部工具演示:保留频道侧边栏和成员目录,将 BRAND 设为你的产品,并将对话替换为你自己的入门或支持工作流。

团队聊天应用界面:常见问题

访客在团队聊天应用界面演示中实际能做什么?

团队聊天应用界面是一个可实际运行的客户端消息工作区,而不是静态模型。访客可以在六个频道和三个私信之间切换、搜索消息、发送新消息、切换表情回应、打开并回复话题串、插入提及和 Unicode emoji、筛选成员目录,以及在深色和浅色主题之间切换。草稿、已发送消息、表情回应和已读状态会保存在 localStorage 中。

团队聊天应用界面可以免费使用吗?Pro 增加了什么?

团队聊天应用界面模板是免费的:其提示词和 DESIGN.md 在 CC BY-NC 4.0 下可供个人非商业使用。商业或客户工作需使用 Pro,Pro 还提供完整提示词和演示源代码的访问权限。模板页面本身公开显示简介、技术栈和变量。

怎么用 AI 做一个团队聊天应用界面?

复制本页的提示词,或者运行 npx vibefather add team-chat-app-interface,把 [BRAND]、[PROJECT]、[TEAM_TYPE]、[WORKSPACE] 换成你自己的内容,再粘贴到 Claude Code、Codex、Cursor 等 AI 编程工具里。在线演示就是用这份提示词原样做出来的。