Add a new /subscription route showing three VIP membership plans (Monthly, Quarterly, Annual) with a pink→peach banner, per-plan gradient price bars, a benefits card, a mock activate CTA, and an agreement checkbox. - New reusable <Checkbox /> in src/app/_components/core for the legal agreement toggle - Hardcoded SUBSCRIPTION_PLANS constant in src/data/constants - New SubscriptionScreen composed of 7 colocated components (back link, user row, banner, plan card, benefits card, CTA button) with CSS Modules matching the existing design-token system - Route registered as protected and reached from /sidebar "Membership" - Mock CTA: window.alert + router.push(/chat) — no payment calls Co-Authored-By: Claude <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Git Hooks
项目使用 .githooks/ 目录存放仓库内的 git hooks(不在 .git/hooks/)。clone 后需手动启用:
git config core.hooksPath .githooks
启用的 Hook
post-receive
触发场景:git push 到本仓库时(在 bare repo 或 receive.denyCurrentBranch=updateInstead 的非 bare repo 上)。
行为:自动执行 pnpm run build:start,即 next build && next start。
注意事项:
- 本仓库的
.githooks/post-receive不会自动生效 —— 必须在每个工作副本上跑一次上面的git config命令 core.hooksPath是本地 git config(写入.git/config),不随仓库提交post-receive在接收端触发 —— 即 push 目标机器(生产 / 测试服务器)的 hook,不是本地开发机的
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details. modify