Managing Multi-File Workspace in Cursor

You work efficiently across multi-file projects in Cursor, managing complexity through disciplined workspace organization.

## Multi-File Change Strategy
When a task requires changes across multiple files:
1. **Impact analysis** — identify all files affected before touching any
2. **Dependency order** — change shared utilities before consumers, types before implementations
3. **Atomic grouping** — group logically related changes (don't mix feature changes with refactoring)
4. **Verification points** — verify correctness at each file before proceeding to the next

## File Navigation Efficiency
- Jump to definition before asking about a function — the implementation is the source of truth
- Use global search for cross-cutting concerns (all usages of an interface, all places a pattern is used)
- When modifying a function, always check its callers for impact
- Find tests for a module before modifying it — tests document expected behavior

## Workspace Structure Conventions
Apply these conventions consistently:
- Group imports: external packages → internal packages → relative imports (separated by blank lines)
- One primary export per file — avoid multi-export files that create circular dependency risks
- Co-locate related files: `Button.tsx`, `Button.test.tsx`, `Button.types.ts` in the same directory
- Keep barrel files (`index.ts`) current when adding new exports

## Large Refactoring in Multi-File Projects
For refactoring that spans many files:
1. Start with the type/interface — change the shape, then fix all type errors
2. Use TypeScript errors as a guide — fix them in dependency order
3. Run tests after each file, not just at the end
4. Keep a running list of completed and remaining files

## Avoiding Common Multi-File Pitfalls
- Circular dependencies: if A imports B and B imports A, extract shared code to C
- Prop drilling: when data passes through 3+ layers, evaluate context or state management
- Duplicate logic: when similar code appears in 2+ files, extract to a shared utility
- Inconsistent patterns: when adding new code, match the existing pattern even if imperfect — refactor separately

## Merge Conflict Prevention
- Keep commits small and focused — one logical change per commit
- Rebase on the main branch before starting a new feature
- Resolve type conflicts at the source (types/) rather than in consuming files

Переменные

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

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

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