Cursor Rules - ReFaceFlow

# Cursor Rules - ReFaceFlow

## Main Rules

### 1. Plan Management

- **MANDATORY**: All plans must be saved in `docs/plans/` numbered sequentially
- Format: `docs/plans/01-<description>.md`, `docs/plans/02-<description>.md`, etc.
- Before creating a new plan, check the last number used and increment
- Each plan must contain: objective, scope, technical requirements, and implementation steps
- **All plans must be written in English**

### 2. External Frameworks and Libraries Implementation

- **MANDATORY**: Before implementing any code that uses:
  - Specific frameworks (DSPy, FastAPI, React, Modal, etc.)
  - Non-built-in libraries for Python/JavaScript
  - External structures or third-party APIs
  
  You MUST:
  1. Create a plan in `docs/plans/` following rule #1
  2. Consult official documentation using the Browser tool
  3. Verify usage examples and best practices
  4. Document design decisions in the plan before implementing

### 3. Code Standards

- **Code must be 100% functional**: No placeholders, unimplemented TODOs, or incomplete code
- **No overengineering**: Avoid unnecessary abstractions, complex design patterns when there's no clear need
- **No verbosity**: Code must be concise and to the point
- **Mandatory docstrings**: All functions must have single-line docstrings in the format:
  ```python
  def function_name(param1, param2):
      """Brief description of what the function does."""
      # implementation
  ```
- Docstrings must be in English, concise and descriptive
- **All code, comments, and docstrings must be in English**

### 4. Language and Format Requirements

- **MANDATORY**: All code, comments, docstrings, and plans must be written in English
- **MANDATORY**: Never use emojis in any structure:
  - No emojis in code comments
  - No emojis in docstrings
  - No emojis in variable names, function names, or any identifiers
  - No emojis in documentation files (markdown, plans, etc.)
  - No emojis in commit messages
  - No emojis in any text-based project files

### 5. Quality and Testing

- Code must be testable and tested when applicable
- Appropriate error handling without silencing important exceptions
- Type hints when possible (Python) or TypeScript (JavaScript/TypeScript)

### 6. File Structure

- Maintain the modular structure of the project
- Follow project naming conventions
- Related code must be logically grouped

---

**Note**: These rules are mandatory and must be followed in all code implementations and modifications.