W701 · Stripe 支付集成 + 多 Agent Persona + SOUL.md 行为边界W701 · Stripe Integration + Multi-Agent Persona + SOUL.md Boundariesv1.0

目录Outline

Stripe 关键概念与链路Stripe Key Concepts and Flow

Stripe Dashboard 准备 + 项目环境配置Stripe Dashboard Setup + Project Configuration

STRIPE_SECRET_KEY=sk_test_xxx
STRIPE_PRICE_ID=price_xxx
APP_BASE_URL=http://localhost:3000

server: {
  port: 3000,
  proxy: {
    '/api': { target: 'http://localhost:8787', changeOrigin: true },
  },
}

AI 实现「订阅按钮 → Stripe 付款页」AI Builds “Subscribe Button → Stripe Checkout”

演示目标：浏览器点“开通 Pro” → 跳到 Stripe 官方付款页。Demo goal: click “Upgrade to Pro” in the browser → redirect to Stripe Checkout.

请在当前项目实现固定金额 Stripe 月订阅入口。

【项目背景】
- 前端栈：【例：React + Vite / Vue / Next.js】
- 后端形态：【例：Cloudflare Worker / Firebase Functions / Express】
- 用户系统：【例：Firebase Auth / Supabase / 自建】
- Stripe Price ID 已配在后端环境变量：STRIPE_PRICE_ID
- Stripe Secret Key 已配在后端环境变量：STRIPE_SECRET_KEY
- 支付完成回跳 URL 环境变量：APP_BASE_URL

【实现要求】
1. 后端暴露接口（如 POST /api/billing/checkout），调 Stripe 创建 Checkout Session 并返回付款页 URL
2. 创建 Session 时把当前登录用户的 ID 通过 client_reference_id 带过去（后续 Webhook 要用）
3. 前端加“开通 Pro”按钮，点击调后端接口拿到 URL 后跳转
4. 支付完成 / 取消都回到 APP_BASE_URL
5. Stripe Secret Key 不能暴露到前端
6. 沿用项目现有代码风格和样式

Implement a fixed-price monthly Stripe subscription entry in the current project.

[Project context]
- Frontend stack: [e.g. React + Vite / Vue / Next.js]
- Backend shape: [e.g. Cloudflare Worker / Firebase Functions / Express]
- User system: [e.g. Firebase Auth / Supabase / custom]
- Stripe Price ID is configured in backend env: STRIPE_PRICE_ID
- Stripe Secret Key is configured in backend env: STRIPE_SECRET_KEY
- Return URL env var: APP_BASE_URL

[Requirements]
1. Expose a backend endpoint such as POST /api/billing/checkout, create a Stripe Checkout Session, and return the Checkout URL
2. Pass the current logged-in user ID through client_reference_id for the later Webhook
3. Add an “Upgrade to Pro” button on the frontend; click it, call the backend, receive the URL, and redirect
4. Both success and cancel return to APP_BASE_URL
5. Never expose the Stripe Secret Key to the frontend
6. Follow the existing project style and code conventions

当场跑通验收：浏览器看到“开通 Pro”按钮 → 点击 → 跳到 Stripe Checkout 页面（显示 Demo Pro Plan · US$9.90/月）→ 前端代码 grep 不到 sk_test。Live check: browser shows “Upgrade to Pro” → click → Stripe Checkout page appears (Demo Pro Plan · US$9.90/month) → frontend code does not contain sk_test.

Stripe CLI 授权与 Webhook 本地监听Stripe CLI Authorization and Local Webhook Listening

stripe login
stripe listen --forward-to localhost:8787/api/billing/webhook

STRIPE_WEBHOOK_SECRET=whsec_xxx

请在后端实现 Stripe Webhook 接收端。

【项目背景】
- 后端形态：【例：Cloudflare Worker / Firebase Functions / Express】
- 用户系统：【例：Firebase Auth / Supabase / 自建】
- 用户订阅状态存储位置：【例：Firestore users/{uid} 文档 subscriptionStatus 字段 / 数据库 users 表 subscription_status 列】
- Stripe Webhook Secret 已配在后端环境变量：STRIPE_WEBHOOK_SECRET

【实现要求】
1. 后端暴露 POST /api/billing/webhook 接口
2. 用 STRIPE_WEBHOOK_SECRET 验证 Stripe Webhook 签名（安全关键，不能跳过）
3. 处理以下事件并更新对应用户的订阅状态：
   - checkout.session.completed → "active"
   - customer.subscription.deleted → "canceled"
   - invoice.payment_failed → "past_due"
4. 通过 Checkout Session 的 client_reference_id 拿到当前用户 ID，定位到具体用户记录
5. 处理完返回 200 状态码（不返 200 Stripe 会重试）
6. 沿用项目现有代码风格

Implement the Stripe Webhook receiver on the backend.

[Project context]
- Backend shape: [e.g. Cloudflare Worker / Firebase Functions / Express]
- User system: [e.g. Firebase Auth / Supabase / custom]
- Subscription state storage: [e.g. Firestore users/{uid}.subscriptionStatus / users.subscription_status]
- Stripe Webhook Secret is configured in backend env: STRIPE_WEBHOOK_SECRET

[Requirements]
1. Expose POST /api/billing/webhook
2. Verify the Stripe Webhook signature with STRIPE_WEBHOOK_SECRET; this is security-critical
3. Handle events and update subscription state:
   - checkout.session.completed → "active"
   - customer.subscription.deleted → "canceled"
   - invoice.payment_failed → "past_due"
4. Use client_reference_id from Checkout Session to locate the current user
5. Return HTTP 200 after processing, otherwise Stripe retries
6. Follow existing project style

支付成功与 Stripe 交易记录验证Payment Success and Stripe Transaction Verification

请把订阅状态接入前端 Pro 功能权限。

【项目背景】
- 前端栈：【例：React + Vite / Vue / Next.js】
- 用户系统：【例：Firebase Auth / Supabase / 自建】
- 订阅状态存储位置：【例：Firestore users/{uid} 文档 subscriptionStatus 字段】
- 当前项目里要变成 Pro 的功能：【例：本演示中是“语音实战面试”，你的项目里替换为对应功能名】

【实现要求】
1. 业务规则：
   - subscriptionStatus 为 active 或 trialing → 可用 Pro 功能
   - 未订阅 / canceled / past_due → 禁用 Pro 功能，显示订阅引导
2. 前端权限判断必须读数据库订阅状态，不要只根据支付回跳 URL 判断
3. 无权限时展示订阅引导（含“开通 Pro”按钮）
4. 有权限时正常展示 Pro 功能
5. 沿用项目现有代码风格

Connect subscription state to frontend Pro feature access.

[Project context]
- Frontend stack: [e.g. React + Vite / Vue / Next.js]
- User system: [e.g. Firebase Auth / Supabase / custom]
- Subscription state storage: [e.g. Firestore users/{uid}.subscriptionStatus]
- Feature to turn into Pro: [e.g. "voice mock interview" in this demo; replace it with your project feature]

[Requirements]
1. Business rules:
   - subscriptionStatus active or trialing → Pro feature available
   - no subscription / canceled / past_due → disable Pro feature and show subscription prompt
2. Frontend access control must read subscription state from database, not just the payment return URL
3. Show subscription prompt with “Upgrade to Pro” when unauthorized
4. Show Pro feature normally when authorized
5. Follow existing project style

支付集成检查清单Payment Integration Checklist

Agent 也需要“人格”Agents Need a Personality Too

SOUL.md 五原则与字段结构SOUL.md Five Principles and Structure

不同 SOUL.md 内容效果对比Effect Comparison of Different SOUL.md Files

气质（硬性规则）：
- 首句必须以"不"、"错了"、"问题在于"
  之一开头
- 禁止使用"加油""你能行""相信自己"
- 禁止以鼓励句结尾
- 一句话能讲完的不写第二句
- 必要时阴阳怪气

Temperament (hard rules):
- First sentence must start with "No",
  "Wrong", or "The problem is"
- Never use "you can do it", "trust
  yourself", or similar encouragement
- Never end with an encouraging line
- If one sentence is enough, don't write
  a second one
- Snark is allowed when warranted

气质（硬性规则）：
- 首句必须是情绪共情
- 禁止首句直接给事实判断或反驳
- 每个建议步骤后必须附鼓励的话
- 结尾必须含"加油"、"你已经做得很好"
  或"慢慢来都来得及"之一
- 多用"我们"、"一起"、"陪你"

Temperament (hard rules):
- First sentence must show emotional
  empathy
- Never start with a fact-based judgment
  or rebuttal
- Each suggestion step must end with
  encouragement
- Ending must contain one of "keep
  going", "you're doing great", or
  "take your time"
- Use "we", "together", "I'm with you"
  often

多 Agent 在飞书群里怎么协作How Multiple Agents Collaborate in Feishu

3 智能体协作链Three-Agent Collaboration Chain

作业Homework