Persistent Workspace Patterns for Cursor

You maintain persistent state and context across a long coding session in this workspace. Use these patterns to keep work organized and resumable.

## Session State Management
At the start of each session, establish:
- Current task and its goal
- Files currently in scope
- Any in-progress changes that need to be completed
- Outstanding decisions waiting for user input

## Workspace Organization
Maintain a clear workspace structure:
- Keep related files open together (component + test + types)
- Close files unrelated to the current task to reduce cognitive load
- Use consistent naming for scratch/temporary work (prefix with `_tmp_` or `_wip_`)
- Document in-progress state in a task note if work spans multiple sessions

## Change Tracking
For multi-file changes:
- List every file that will be modified before starting
- Apply changes in a logical order (dependencies before dependents)
- After completing a group of related changes, checkpoint with a clear description
- Keep unrelated changes in separate commits even within the same session

## Context Persistence Patterns
When context must survive across sessions:
- Write key decisions to inline comments rather than relying on memory
- Use TODO/FIXME comments with context: `// TODO(auth): handle token expiry case — see issue #42`
- Document non-obvious constraints at module level: `// NOTE: This module must remain synchronous — see perf analysis`
- Keep a `NOTES.md` or similar file for session-level working notes in long projects

## Resumability
Design your work session to be interruptible:
- Never leave files in a broken intermediate state — if you must stop mid-change, revert the partial change
- Before ending a session, write a brief status note: what's done, what's in progress, what's next
- Keep test suite green at each checkpoint — a red test suite is a poor stopping point

## Conflict Avoidance
When working in a shared repository:
- Pull latest changes before starting a new editing session
- Keep changes focused — broad reformatting in the same commit as logic changes creates merge conflicts
- Communicate pending large changes before starting them in a team context

Переменные

Нет переменных

Цели экспорта

Используется в паках