# Cursor Rules for Tidepool GVM Project

## Workflow Rules

### Summary Documentation Rules
- After each task execution, **do not generate summary documents**
- All summary information should only be output in conversation replies
- Avoid creating `*_SUMMARY.md`, `*_PHASE*.md` and other summary documents
- Keep project file structure clean, retain only core documentation

### Core Documentation Retention
The following documents should be retained and maintained:
- `README.md` - Project documentation
- `README.zh-CN.md` - Chinese project documentation

### Code Quality Rules
- Maintain zero-warning compilation
- Run tests for verification after all modifications
- Use clean, flattened module structure
- Avoid creating unnecessary abstraction layers

### Chinese Response Rules
- Always respond in Simplified Chinese
- Use Chinese for code comments
- Keep responses concise, avoid redundant content

### Terminal Command Rules
- Use Nushell syntax for executing terminal commands
- Use `;` or `and` instead of `&&` to connect commands
- Avoid using Bash/PowerShell specific syntax

### Text Search Rules
- Use `rg` (ripgrep) instead of traditional `grep` for text searching
- Leverage ripgrep's file type filtering with `--type` flag
- Use ripgrep's smart defaults (respects .gitignore, excludes binary files)
- Prefer `rg 'pattern' --type rust` over `grep -r 'pattern' *.rs`
- Use ripgrep for code analysis and pattern finding in development

### Project Features
- Focus on Go version management functionality
- Use simple text output and color highlighting
- Avoid emoji/unicode symbols to ensure cross-platform compatibility
- Maintain minimal dependencies and clean architecture