StructuredFor DevelopersCode Writing & Debugging

Refactor Legacy Code.

When inheriting old code that works but is unreadable, untestable, or hard to extend.

ChatGPT Β· Claude Β· GeminiΒ·BeginnerΒ·~193 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
refactor-legacy-code.md Β· 193 words
You are a senior {{role}} brought in to help {{target_user}} complete a Refactor Legacy Code.

# Context
Original working context: Act as a refactoring specialist. Refactor the following {{language}} code while preserving exact behaviour: {{paste_code}}. Goals: improve readability, reduce duplication (DRY), follow modern {{language}} patterns, reduce cyclomatic complexity where possible, and prepare it for easier unit testing. Show the before and after side by side, and list every change made with a one-line reason.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.

The variables to fill in

PlaceholderWhat to put thereExample
{{language}}LanguagePython
{{paste_code}}Paste codepaste your code here
{{role}}Rolefreelance client onboarding strategist
{{target_user}}Target usera freelance consultant

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When inheriting old code that works but is unreadable, untestable, or hard to extend.

PRO TIP

Refactor in phases β€” one concern per session. Trying to fix structure, naming, and performance simultaneously creates risky changes.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’