# Project Rules

## Tech Stack
- Frontend: Next.js 14 (App Router), Tailwind CSS, TypeScript
- Backend: Supabase, tRPC
- Testing: Vitest + Playwright

## NEVER
- Use `any` type in TypeScript
- Introduce new dependencies without approval
- Modify `src/legacy/` folder — it's deprecated
- Skip writing tests for new features

## ALWAYS
- Use server components by default, client components only when needed
- Follow the existing error handling pattern with `Result<T, E>` type
- Keep components under 200 lines

# Boris Mode

## How I Think
- I prefer clarity over cleverness. If a solution is too smart, simplify it.
- I prioritize developer experience and readability.
- I'd rather have 5 simple functions than 1 complex abstraction.

## How I Code
- I prototype fast, refactor later
- I write tests only for business logic, not for UI
- I prefer functional composition over class inheritance

## My Pet Peeves
- Over-engineered patterns that solve problems I don't have
- Premature optimization
- Configuration files that require reading docs to understand

## Current Focus
- Shipping the onboarding flow this sprint
- Reducing bundle size by 20%
- Cleaning up tech debt in the auth module

# Local overrides (don't commit)

## My Tools
- I use Warp terminal with custom aliases
- My preferred AI tool for quick Q&A is `claude` CLI
- Local DB runs on port 5433, not 5432

## My Style
- I like verbose comments in Chinese for complex logic
- I prefer async/await over Promise chains
- I use zod for runtime validation even in internal code

## Experimental
- Testing out Biome as ESLint replacement
- Trying `bun` for script running (faster than tsx)

---
name: api-designer
description: RESTful API 设计最佳实践——自动检查端点命名、错误码、分页规范
---

# API Designer Skill

## Rules
- All endpoints use `/api/v1/` prefix
- Error responses follow RFC 7807 (Problem Details)
- Pagination uses cursor-based (not offset-based)
- Rate limiting headers must be included in all responses

## Check when reviewing API code
1. Are error codes consistent (4xx for client, 5xx for server)?
2. Is pagination response wrapped in `{ data: [], next_cursor: string | null }`?
3. Are all input fields validated with zod schemas?
4. Do DELETE endpoints return 204 with no body?

## Anti-patterns
- Don't nest resources deeper than 2 levels
- Don't use verbs in URLs (`/getUser` → GET `/users/:id`)
- Don't return raw DB errors to clients

## Active Skills
- `.claude/skills/api-designer.md` — API 设计审查
- `.claude/skills/db-query-optimizer.md` — SQL 查询优化

---
name: pr-reviewer
description: 代码审查清单——自动检查安全、性能、可维护性问题
---

# PR Reviewer Skill

## Security Checklist
- [ ] User input is validated AND sanitized
- [ ] No secrets/tokens in code
- [ ] SQL queries use parameterized statements
- [ ] Auth checks on every protected endpoint

## Performance Checklist
- [ ] No N+1 queries
- [ ] Large lists are paginated
- [ ] Expensive computations are memoized
- [ ] Images are lazy-loaded

## Maintainability Checklist
- [ ] Function name describes what it does
- [ ] No magic numbers (use named constants)
- [ ] Error messages are actionable
- [ ] New code has tests

## Review Comment Template
当发现问题时，用以下格式给出建议：
**🔴 [严重程度] 文件名:行号**
问题描述 → 为什么是问题 → 建议修改方案

---
name: commit-msg
description: 生成符合 Conventional Commits 规范的提交信息
---

# Commit Message Skill

## Format
`<type>(<scope>): <description>`

## Types
- `feat`: 新功能
- `fix`: Bug 修复
- `refactor`: 重构（不改变行为）
- `perf`: 性能优化
- `test`: 测试相关
- `docs`: 文档
- `chore`: 构建/工具

## Rules
- Description 用英文，50 字符以内
- 重大变更加 `BREAKING CHANGE:` 页脚
- 关联 Issue 用 `Closes #123`

---
name: cn-tech-writer
description: 中文技术文档写作规范
---

# 中文技术写作规范

## 排版
- 中英文之间加空格：`使用 React 开发`
- 数字与单位之间加空格：`100 MB`
- 代码用反引号包裹：`useState`

## 术语
- 专有名词保持原文大小写：`GitHub`，不是 `github`
- 首次出现的英文术语给出中文解释后括号标注原文
- 技术概念用「」标注，非书名号《》

## 风格
- 用「你」而非「您」
- 主动语态优先
- 每个段落一个核心观点
- 代码块必须标注语言

# 而不是：
> 帮我创建一个 Next.js 项目，用 TypeScript，加 Tailwind，配好 ESLint...

# 试试：
> /goal 我要从零搭建一个简单的博客项目，技术栈 Next.js + MDX

# CLAUDE.md — Project Context

## Project: [项目名称]
## Stack: [技术栈]

---

## My Coding Philosophy (Boris Mode)
- 清晰 > 聪明
- 5 个简单函数 > 1 个复杂抽象
- 先用最直接的方案，跑通了再优化
- 测试只写给业务逻辑，不给 UI 写

## Project Rules
- NEVER: [你的禁区]
- ALWAYS: [你的铁律]
- PREFER: [你的偏好]

## Active Skills
- .claude/skills/api-designer.md
- .claude/skills/pr-reviewer.md

## File Structure
src/
├── app/          # Next.js App Router 页面
├── components/   # 可复用组件（<200 行）
├── lib/          # 工具函数
├── server/       # 服务端逻辑（tRPC routers）
└── types/        # 共享类型定义

## Common Commands
- `pnpm dev` — 启动开发服务器
- `pnpm test` — 运行测试
- `pnpm lint` — 代码检查

## Current Sprint
- [当前重点任务1]
- [当前重点任务2]