# foodie_server Development Guidelines

Auto-generated from all feature plans. Last updated: 2026-04-29

## Active Technologies

- [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION] + [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION] (master)

## Project Structure

```text
平台管理前端代码路径：E:\QtwCode\foodie\foodie-admin-vue
商家端管理前端代码路径：E:\QtwCode\foodie\foodie-store
```

## Commands

cd src; pytest; ruff check .

## Code Style

[e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]: Follow standard conventions

## Recent Changes

- master: Added [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION] + [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]

<!-- MANUAL ADDITIONS START -->

## 前端多语言(i18n)添加规范

商家端(foodie-store)使用 vue-i18n，语言文件在 `src/lang/` 下（zh.js、tw.js、en.js、vi.js）。

**添加多语言 key 时必须注意：**

1. **先确认 key 所属的对象层级。** 语言文件中有多层嵌套对象（如 `foots:{}`、`cuxiao:{}`、`fenlei:{}` 等），使用 `$t('foots.XXX')` 的 key 必须添加到 `foots` 对象**内部**，不能加到文件顶部或其它对象里。
2. **找到该对象的最后一个属性**（通过 grep 或阅读文件定位），在其后追加新 key，确保逗号正确（中间属性末尾要有逗号，最后一个属性无逗号）。
3. **四个语言文件（zh.js、tw.js、en.js、vi.js）都要添加**，缺一不可。

**曾经犯的错误：** 把 `AddCategoryFirst` 加到了文件第 141 行的公共区域，而 `$t('foots.AddCategoryFirst')` 是在 `foots` 对象（第 190+ 行）下查找，导致页面显示原始 key 而非翻译文本。

## 前端文件编辑注意事项

前端项目（foodie-store、foodie-admin-vue）的文件使用 **CRLF 换行符**（Windows 风格 `\r\n`）。使用编辑工具进行字符串替换时，由于换行符不匹配会导致 "String to replace not found" 错误。

**正确做法：** 编辑前端文件时，使用 Python 脚本（`python << 'PYEOF'`）通过 `content.replace()` 或行号操作来修改文件内容，避免换行符匹配问题。

<!-- MANUAL ADDITIONS END -->
# CLAUDE.md

Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.

**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.

## 1. Think Before Coding

**Don't assume. Don't hide confusion. Surface tradeoffs.**

Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.

## 2. Simplicity First

**Minimum code that solves the problem. Nothing speculative.**

- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.

Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

## 3. Surgical Changes

**Touch only what you must. Clean up only your own mess.**

When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.

When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.

The test: Every changed line should trace directly to the user's request.

## 4. Goal-Driven Execution

**Define success criteria. Loop until verified.**

Transform tasks into verifiable goals:
- "Add validation" → "Write tests for invalid inputs, then make them pass"
- "Fix the bug" → "Write a test that reproduces it, then make it pass"
- "Refactor X" → "Ensure tests pass before and after"

For multi-step tasks, state a brief plan:
```
1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]
```

Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

---

**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.
