RefactoringIntermediate2 variants

Refactor Safety Review

Ask Cursor to identify behavior-preserving refactor risks before touching shared modules.

Placeholders

{{CALLERS}}{{CURRENT_MODULE}}{{REFACTOR_GOAL}}{{TESTS_AVAILABLE}}

Base template

I am planning a behavior-preserving refactor.

Current module: {{CURRENT_MODULE}}

Refactor goal: {{REFACTOR_GOAL}}

Known callers: {{CALLERS}}

Existing tests: {{TESTS_AVAILABLE}}

Before writing code, identify the invariants that must not change, missing tests to add first, migration steps, and rollback risks.

Stack Variants

TypeScript Shared Library

Extracting helpers used across app routes and components

Variant

Review this TypeScript refactor plan for shared-library risk.

Module: {{CURRENT_MODULE}}

Goal: {{REFACTOR_GOAL}}

Callers: {{CALLERS}}

Tests: {{TESTS_AVAILABLE}}

List type-level invariants, runtime behavior invariants, import-cycle risks, and the minimum test matrix before code changes.

Notes

Helps prevent broad helper refactors from changing response text or error semantics.
Ask for caller categories rather than a single happy-path test.

React Component Split

Breaking up large UI components

Variant

Evaluate this React component split before implementation.

Component: {{CURRENT_MODULE}}

Goal: {{REFACTOR_GOAL}}

Callers: {{CALLERS}}

Tests: {{TESTS_AVAILABLE}}

Identify prop boundaries, state that should stay colocated, accessibility behaviors that must be preserved, and RTL tests that should be added before the split.

Notes

Use this before decomposing page components with forms, modals, or keyboard behavior.
Keep state ownership explicit so the split does not create sync bugs.