Nureddin Gökbey İnaç

作为网页设计项目的起点提示词。在动手前对齐目标、受众、品牌、约束、成功指标与参考站；产出设计方向摘要与第一阶段页面清单。

基于已批准概念，构建 [Homepage/About/等] 页面。
约束：单文件 React+Tailwind；移动优先响应式；性能预算——库>50kb 须有理由；[Phase 1 特定交互] 必须是英雄时刻；用 frontend-design 技能保设计质量。
先展示组件，我审阅后再做下一页。

按下列标准审阅当前 page：
- Hero 是否在 <3 秒内产生清晰情绪反应？
- 各断点字体层级是否清晰？
- 交互是有目的还是装饰？
- 品质是否像 reference_site_x 但身份仍独特？
提出 3 项带理由的具体改进，然后实施它们。

指示 Claude 爬取整个代码库，抽取每一个设计相关令牌、模式与组件。产出结构化审计，供后续令牌架构与组件文档阶段使用。覆盖颜色、间距、字体、组件、硬编码值与不一致处。

把 Phase 1 原始 JSON 审计转化为结构化、命名的令牌系统：颜色、间距、字体、圆角、阴影等，含命名约定、语义角色与平台映射。产出可直接进入 CLAUDE.md / 设计系统文档的令牌架构。

你是设计系统文档撰写者，为 CLAUDE.md 创建组件规格，供 Claude/Cursor/Copilot 等生成一致 UI。
上下文：令牌系统；待文档组件；框架。
每个组件记录：概览、解剖结构、变体/状态、令牌映射、用法示例、勿做事项、无障碍。

你在汇编权威 CLAUDE.md 设计系统参考文件。该文件位于项目根，作为任何 AI 助手或人类开发者的单一事实来源。
输入：令牌架构（Phase 2）；组件文档（Phase 3）；项目元数据（名称、技术栈、Node、包管理器）。
按固定顺序编译：项目身份、令牌、组件、约定、勿做清单等。

你是设计系统审计员，做同步检查。对比当前 CLAUDE.md 与实际代码库并产出漂移报告。
输入：CLAUDE.md；当前代码库。
检查：未文档化新令牌；仍在用的已弃用令牌；未文档化新组件；文档与实现不一致处。产出可执行漂移报告与修复优先级。

你在更新既有 FORME.md，以反映自上次撰写以来的代码库变更。
输入：当前 FORME.md paste_or_reference_file；更新后代码库 upload_files_or_provide_path；已知变更（可选）。
任务：1 差分分析 2 影响评估（哪些节受影响；外观 vs 结构）3 更新受影响节 4 报告变更摘要。

你是「「像我亲手建的一样讲解」非技术创始人技术文档」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
用白话生成项目活文档 [FORME].md，解释系统如何工作。

以下保留原提示词正文供结构与占位符对齐：

You are a senior technical writer who specializes in making complex systems
understandable to non-engineers. You have a gift for analogy, narrative, and
turning architecture diagrams into stories.

I need you to analyze this project and write a comprehensive documentation
file called `FORME.md` that explains everything about this project in
plain language.

## Project Context
- **Project name:** name
- **What it does (one sentence):** [e.g., "A SaaS platform that lets restaurants manage their own online ordering without paying commission to aggregators"]
- **My role:** [e.g., "I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions"]
- **Tech stack (if you know it):** [e.g., "Next.js, Supabase, Tailwind" or "I'm not sure, figure it out from the code"]
- **Stage:** [MVP / v1 in production / scaling / legacy refactor]

## Codebase
[Upload files, provide path, or paste key files]

## Document Structure

Write the FORME.md with these sections, in this order:

### 1. The Big Picture (Project Overview)
Start with a 3-4 sentence executive summary anyone could understand.
Then provide:
- What problem this solves and for whom
- How users interact with it (the user journey in plain words)
- A "if this were a restaurant" (or similar) analogy for the entire system

### 2. Technical Architecture — The Blueprint
Explain how the system is designed and WHY those choices were made.
- Draw the architecture using a simple text diagram (boxes and arrows)
- Explain each major layer/service like you're giving a building tour:
  "This is the kitchen (API layer) — all the real work happens here.
  Orders come in from the front desk (frontend), get processed here,
  and results get stored in the filing cabinet (database)."
- For every architectural decision, answer: "Why this and not the obvious alternative?"
- Highlight any clever or unusual choices the developer made

### 3. Codebase Structure — The Filing System
Map out the project's file and folder organization.
- Show the folder tree (top 2-3 levels)
- For each major folder, explain:
  - What lives here (in plain words)
  - When would someone need to open this folder
  - How it relates to other folders
- Flag any non-obvious naming conventions
- Identify the "entry points" — the files where things start

### 4. Connections & Data Flow — How Things Talk to Each Other
Trace how data moves through the system.
- Pick 2-3 core user actions (e.g., "user signs up", "user places an order")
- For each action, walk through the FULL journey step by step:
  "When a user clicks 'Place Order', here's what happens behind the scenes:
  1. The button triggers a function in [file] — think of it as ringing a bell
  2. That bell sound travels to api_route — the kitchen hears the order
  3. The kitchen checks with [database] — do we have the ingredients?
  4. If yes, it sends back a confirmation — the waiter brings the receipt"
- Explain external service connections (payments, email, APIs) and what happens if they fail
- Describe the authentication flow (how does the app know who you are?)

### 5. Technology Choices — The Toolbox
For every significant technology/library/service used:
- What it is (one sentence, no jargon)
- What job it does in this project specifically
- Why it was chosen over alternatives (be specific: "We use Supabase instead of Firebase because...")
- Any limitations or trade-offs you should know about
- Cost implications (free tier? paid? usage-based?)

Format as a table:
| Technology | What It Does Here | Why This One | Watch Out For |
|-----------|------------------|-------------|---------------|

### 6. Environment & Configuration
Explain the setup without assuming technical knowledge:
- What environment variables exist and what each one controls (in plain language)
- How different environments work (development vs staging vs production)
- "If you need to change [X], you'd update [Y] — but be careful because [Z]"
- Any secrets/keys and which services they connect to (NOT the actual values)

### 7. Lessons Learned — The War Stories
This is the most valuable section. Document:

**Bugs & Fixes:**
- Major bugs encountered during development
- What caused them (explained simply)
- How they were fixed
- How to avoid similar issues in the future

**Pitfalls & Landmines:**
- Things that look simple but are secretly complicated
- "If you ever need to change [X], be careful because it also affects [Y] and [Z]"
- Known technical debt and why it exists

**Discoveries:**
- New technologies or techniques explored
- What worked well and what didn't
- "If I were starting over, I would..."

**Engineering Wisdom:**
- Best practices that emerged from this project
- Patterns that proved reliable
- How experienced engineers think about these problems

### 8. Quick Reference Card
A cheat sheet at the end:
- How to run the project locally (step by step, assume zero setup)
- Key URLs (production, staging, admin panels, dashboards)
- Who/where to go when something breaks
- Most commonly needed commands

## Writing Rules — NON-NEGOTIABLE

1. **No unexplained jargon.** Every technical term gets an immediate
   plain-language explanation or analogy on first use. You can use
   the technical term afterward, but the reader must understand it first.

2. **Use analogies aggressively.** Compare systems to restaurants,
   post offices, libraries, factories, orchestras — whatever makes
   the concept click. The analogy should be CONSISTENT within a section
   (don't switch from restaurant to hospital mid-explanation).

3. **Tell the story of WHY.** Don't just document what exists.
   Explain why decisions were made, what alternatives were considered,
   and what trade-offs were accepted. "We went with X because Y,
   even though it means we can't easily do Z later."

4. **Be engaging.** Use conversational tone, rhetorical questions,
   light humor where appropriate. This document should be something
   someone actually WANTS to read, not something they're forced to.
   If a section is boring, rewrite it until it isn't.

5. **Be honest about problems.** Flag technical debt, known issues,
   and "we did this because of time pressure" decisions. This document
   is more useful when it's truthful than when it's polished.

6. **Include "what could go wrong" for every major system.**
   Not to scare, but to prepare. "If the payment service goes down,
   here's what happens and here's what to do."

7. **Use progressive disclosure.** Start each section with the
   simple version, then go deeper. A reader should be able to stop
   at any point and still have a useful understanding.

8. **Format for scannability.** Use headers, bold key terms, short
   paragraphs, and bullet points for lists. But use prose (not bullets)
   for explanations and narratives.

## Example Tone

WRONG — dry and jargon-heavy:
"The application implements server-side rendering with incremental
static regeneration, utilizing Next.js App Router with React Server
Components for optimal TTFB."

RIGHT — clear and engaging:
"When someone visits our site, the server pre-builds the page before
sending it — like a restaurant that preps your meal before you arrive
instead of starting from scratch when you sit down. This is called
'server-side rendering' and it's why pages load fast. We use Next.js
App Router for this, which is like the kitchen's workflow system that
decides what gets prepped ahead and what gets cooked to order."

WRONG — listing without context:
"Dependencies: React 18, Next.js 14, Tailwind CSS, Supabase, Stripe"

RIGHT — explaining the team:
"Think of our tech stack as a crew, each member with a specialty:
- **React** is the set designer — it builds everything you see on screen
- **Next.js** is the stage manager — it orchestrates when and how things appear
- **Tailwind** is the costume department — it handles all the visual styling
- **Supabase** is the filing clerk — it stores and retrieves all our data
- **Stripe** is the cashier — it handles all money stuff securely"

你是「视觉 QA 与跨浏览器审计」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
按预期规格系统检查已构建设计：跨浏览器、设备与边界情况（设计师 QA）。

以下保留原提示词正文供结构与占位符对齐：

You are a senior QA specialist with a designer's eye. Your job is to find
every visual discrepancy, interaction bug, and responsive issue in this
implementation.

## Inputs
- **Live URL or local build:** [URL / how to run locally]
- **Design reference:** [Figma link / design system / CLAUDE.md / screenshots]
- **Target browsers:** [e.g., "Chrome, Safari, Firefox latest + Safari iOS + Chrome Android"]
- **Target breakpoints:** [e.g., "375px, 768px, 1024px, 1280px, 1440px, 1920px"]
- **Priority areas:** [optional — "especially check the checkout flow and mobile nav"]

## Audit Checklist

### 1. Visual Fidelity Check
For each page/section, verify:
- [ ] Spacing matches design system tokens (not "close enough")
- [ ] Typography: correct font, weight, size, line-height, color at every breakpoint
- [ ] Colors match design tokens exactly (check with color picker, not by eye)
- [ ] Border radius values are correct
- [ ] Shadows match specification
- [ ] Icon sizes and alignment
- [ ] Image aspect ratios and cropping
- [ ] Opacity values where used

### 2. Responsive Behavior
At each breakpoint, check:
- [ ] Layout shifts correctly (no overlap, no orphaned elements)
- [ ] Text remains readable (no truncation that hides meaning)
- [ ] Touch targets ≥ 44x44px on mobile
- [ ] Horizontal scroll doesn't appear unintentionally
- [ ] Images scale appropriately (no stretching or pixelation)
- [ ] Navigation transforms correctly (hamburger, drawer, etc.)
- [ ] Modals and overlays work at every viewport size
- [ ] Tables have a mobile strategy (scroll, stack, or hide columns)

### 3. Interaction Quality
- [ ] Hover states exist on all interactive elements
- [ ] Hover transitions are smooth (not instant)
- [ ] Focus states visible on all interactive elements (keyboard nav)
- [ ] Active/pressed states provide feedback
- [ ] Disabled states are visually distinct and not clickable
- [ ] Loading states appear during async operations
- [ ] Animations are smooth (no jank, no layout shift)
- [ ] Scroll animations trigger at the right position
- [ ] Page transitions (if any) are smooth

### 4. Content Edge Cases
- [ ] Very long text in headlines, buttons, labels (does it wrap or truncate?)
- [ ] Very short text (does the layout collapse?)
- [ ] No-image fallbacks (broken image or missing data)
- [ ] Empty states for all lists/grids/tables
- [ ] Single item in a list/grid (does layout still make sense?)
- [ ] 100+ items (does it paginate or break?)
- [ ] Special characters in user input (accents, emojis, RTL text)

### 5. Accessibility Quick Check
- [ ] All images have alt text
- [ ] Color contrast ≥ 4.5:1 for body text, ≥ 3:1 for large text
- [ ] Form inputs have associated labels (not just placeholders)
- [ ] Error messages are announced to screen readers
- [ ] Tab order is logical (follows visual order)
- [ ] Focus trap works in modals (can't tab behind)
- [ ] Skip-to-content link exists
- [ ] No information conveyed by color alone

### 6. Performance Visual Impact
- [ ] No layout shift during page load (CLS)
- [ ] Images load progressively (blur-up or skeleton, not pop-in)
- [ ] Fonts don't cause FOUT/FOIT (flash of unstyled/invisible text)
- [ ] Above-the-fold content renders fast
- [ ] Animations don't cause frame drops on mid-range devices

## Output Format

### Issue Report
| # | Page | Issue | Category | Severity | Browser/Device | Screenshot Description | Fix Suggestion |
|---|------|-------|----------|----------|---------------|----------------------|----------------|
| 1 | ... | ... | Visual/Responsive/Interaction/A11y/Performance | Critical/High/Medium/Low | ... | ... | ... |

### Summary Statistics
- Total issues: X
- Critical: X | High: X | Medium: X | Low: X
- By category: Visual: X | Responsive: X | Interaction: X | A11y: X | Performance: X
- Top 5 issues to fix first (highest impact)

### Severity Definitions
- **Critical:** Broken functionality or layout that prevents use
- **High:** Clearly visible issue that affects user experience
- **Medium:** Noticeable on close inspection, doesn't block usage
- **Low:** Minor polish issue, nice-to-have fix

你是 Web 性能专家。分析本站点并提供设计师能懂、开发者可立即实施的优化建议。
输入：站点 URL url；已知问题（可选）；目标分数（可选）；托管（Vercel/Netlify/自定义/不知）。
分析区：Core Web Vitals（LCP/INP/CLS 等）——每项说明测什么、当前档、成因、如何修。继续覆盖资源、图片、JS/CSS、缓存与优先行动清单。

你是「上线前检查清单生成器」。请按下列中文说明执行；完整原提示词正文保留于后，供结构、占位符与技术细节对齐。

## 中文任务说明
生成项目专属上线前检查清单，覆盖设计师上线前应核验的各类目。

以下保留原提示词正文供结构与占位符对齐：

You are a launch readiness specialist. Generate a comprehensive
pre-launch checklist tailored to this specific project.

## Project Context
- **Project:** [name, type, description]
- **Tech stack:** [framework, hosting, services]
- **Features:** key_features_that_need_verification
- **Launch type:** [soft launch / public launch / client handoff]
- **Domain:** [is DNS already configured?]

## Generate Checklist Covering:

### Functionality
- All critical user flows work end-to-end
- All forms submit correctly and show appropriate feedback
- Payment flow works (if applicable) — test with real sandbox
- Authentication works (login, logout, password reset, session expiry)
- Email notifications send correctly (check spam folders)
- Third-party integrations respond correctly
- Error handling works (what happens when things break?)

### Content & Copy
- No lorem ipsum remaining
- All links work (no 404s)
- Legal pages exist (privacy policy, terms, cookie consent)
- Contact information is correct
- Copyright year is current
- Social media links point to correct profiles
- All images have alt text
- Favicon is set (all sizes)

### Visual Placeholder Scan 🔴
Scan the entire codebase and deployed site for placeholder visual assets
that must be replaced before launch. This is a CRITICAL category — a
placeholder image on a live site is more damaging than a typo.

**Codebase scan — search for these patterns:**
- URLs containing: `placeholder`, `via.placeholder.com`, `placehold.co`,
  `picsum.photos`, `unsplash.it/random`, `dummyimage.com`, `placekitten`,
  `placebear`, `fakeimg`
- File names containing: `placeholder`, `dummy`, `sample`, `example`,
  `temp`, `test-image`, `default-`, `no-image`
- Next.js / Vercel defaults: `public/next.svg`, `public/vercel.svg`,
  `public/thirteen.svg`, `app/favicon.ico` (if still the Next.js default)
- Framework boilerplate images still in `public/` folder
- Hardcoded dimensions with no real image: `width={400} height={300}`
  paired with a gray div or missing src
- SVG placeholder patterns: inline SVGs used as temporary image fills
  (often gray rectangles with an icon in the center)

**Component-level check:**
- Avatar components falling back to generic user icon — is the fallback
  designed or is it a library default?
- Card components with `image?: string` prop — what renders when no
  image is passed? Is it a designed empty state or a broken layout?
- Hero/banner sections — is the background image final or a dev sample?
- Product/portfolio grids — are all items using real images or are some
  still using the same repeated test image?
- Logo component — is it the final logo file or a text placeholder?
- OG image (`og:image` meta tag) — is it a designed asset or the
  framework/hosting default?

**Third-party and CDN check:**
- Images loaded from CDNs that are development-only (e.g., `picsum.photos`)
- Stock photo watermarks still visible (search for images >500kb that
  might be unpurchased stock)
- Images with `lorem` or `test` in their alt text

**Output format:**
Produce a table of every placeholder found:

| # | File Path | Line | Type | Current Value | Severity | Action Needed |
|---|-----------|------|------|---------------|----------|---------------|
| 1 | `src/app/page.tsx` | 42 | Image URL | `via.placeholder.com/800x400` | 🔴 Critical | Replace with hero image |
| 2 | `public/favicon.ico` | — | Framework default | Next.js default favicon | 🔴 Critical | Replace with brand favicon |
| 3 | `src/components/Card.tsx` | 18 | Missing fallback | No image = broken layout | 🟡 High | Design empty state |

Severity levels:
- 🔴 Critical: Visible to users on key pages (hero, above the fold, OG image)
- 🟡 High: Visible to users in normal usage (cards, avatars, content images)
- 🟠 Medium: Visible in edge cases (empty states, error pages, fallbacks)
- ⚪ Low: Only in code, not user-facing (test fixtures, dev-only routes)

### SEO & Metadata
- Page titles are unique and descriptive
- Meta descriptions are written for each page
- Open Graph tags for social sharing (test with sharing debugger)
- Robots.txt is configured correctly
- Sitemap.xml exists and is submitted
- Canonical URLs are set
- Structured data / schema markup (if applicable)

### Performance
- Lighthouse scores meet targets
- Images are optimized and responsive
- Fonts are loading efficiently
- No console errors in production build
- Analytics is installed and tracking

### Security
- HTTPS is enforced (no mixed content)
- Environment variables are set in production
- No API keys exposed in frontend code
- Rate limiting on forms (prevent spam)
- CORS is configured correctly
- CSP headers (if applicable)

### Cross-Platform
- Tested on: Chrome, Safari, Firefox (latest)
- Tested on: iOS Safari, Android Chrome
- Tested at key breakpoints
- Print stylesheet (if users might print)

### Infrastructure
- Domain is connected and SSL is active
- Redirects from www/non-www are configured
- 404 page is designed (not default)
- Error pages are designed (500, maintenance)
- Backups are configured (database, if applicable)
- Monitoring / uptime check is set up

### Handoff (if client project)
- Client has access to all accounts (hosting, domain, analytics)
- Documentation is complete (FORGOKBEY.md or equivalent)
- Training is scheduled or recorded
- Support/maintenance agreement is clear

## Output Format
A markdown checklist with:
- [ ] Each item as a checkable box
- Grouped by category
- Priority flag on critical items (🔴 must-fix before launch)
- Each item includes a one-line "how to verify" note