language-preferences

Language and Interaction Preferences

Unified interaction language and communication standards to ensure clear and efficient collaboration.

Language Usage Rules

Scenario	Language
User Questions	Chinese
Internal Execution	English (tool commands, prompts, code comments)
User Responses	Chinese (progress updates, final answers, explanations)
Code Artifacts	Keep original (don't translate)

Content That Must Not Be Translated

Absolutely don't translate:

• Code identifiers (variable names, function names, class names)
• File paths
• Commands and scripts
• Error messages and log output
• Configuration file keys
• API endpoints
• Environment variable names
• Package names

Examples:

// ✅ Keep original
interface UserConfig {
  apiKey: string;        // Don't translate to api密钥
  maxRetries: number;    // Don't translate to 最大重试次数
}

const API_ENDPOINT = '/api/v1/users';  // Don't translate

✅ Keep error messages original:
Error: Cannot find module 'typescript'
TypeError: Cannot read property 'value' of undefined

❌ Don't translate to:
错误: 无法找到模块 'typescript'

Requirement Clarification Process

When requirements are unclear or ambiguous:

1. Identify unclear requirements
2. Ask clarifying questions in Chinese
3. Wait for user feedback
4. Continue work based on feedback

Example:

User: "Help me optimize this function"

Response:
"I need more information to help optimize this function:

1. What aspect are you mainly concerned about?
   - Performance (execution speed)
   - Code readability
   - Memory usage
   - Code conciseness

2. Does this function have performance bottlenecks?

3. Are there any specific constraints?"

Examples

Configuring Project

User asks: "How to configure ESLint?"

✅ Correct response:
"I'll help you configure ESLint. First install dependencies:

Run command:
npm install --save-dev eslint @typescript-eslint/parser

Then create .eslintrc.json config file in project root..."

❌ Wrong response (translated commands):
"Run npm 安装 --保存-开发 eslint..."