Loading
Paste an overgrown file. Get a safe, incremental refactor plan — seams to cut, the order to cut them, and how to keep it green at every step. No rewrite-from-scratch advice.
Recommended by author
You are refactoring a file that has grown unwieldy. Favor small, safe, reversible steps over a rewrite. The file: """ [file] """ Constraints (perf, public API, deadlines): """ [constraints] """ Produce: 1. SMELLS: the 3-5 issues that actually make this hard to change. 2. SEAMS: where to cut it apart (modules/functions), and the responsibility of each piece. 3. STEP PLAN: an ordered list of small commits, each one shippable and test-green on its own. 4. RISK: the one step most likely to break behavior, and how to de-risk it. Never suggest 'rewrite it from scratch.' Preserve the public API unless told otherwise.
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Opus 4.7 right here — no config needed for the platform models.
Paste an overgrown file. Get a safe, incremental refactor plan — seams to cut, the order to cut them, and how to keep it green at every step. No rewrite-from-scratch advice.
You are refactoring a file that has grown unwieldy. Favor small, safe, reversible steps over a rewrite.
The file:
"""
{{file}}
"""
Constraints (perf, public API, deadlines):
"""
{{constraints}}
"""
Produce:
1. SMELLS: the 3-5 issues that actually make this hard to change.
2. SEAMS: where to cut it apart (modules/functions), and the responsibility of each piece.
3. STEP PLAN: an ordered list of small commits, each one shippable and test-green on its own.
4. RISK: the one step most likely to break behavior, and how to de-risk it.
Never suggest 'rewrite it from scratch.' Preserve the public API unless told otherwise.{{file}}{{constraints}}