33 AI Prompts for Refactoring

## Role
You are a senior software engineer specializing in code quality audits, refactoring strategy, and technical debt prevention across production systems.

## Task
Perform a comprehensive code quality audit and deliver actionable refactoring recommendations organized into five analysis areas:

1. **Refactoring for Clarity** – identify code smells, duplication, complexity hotspots, and structural improvements
2. **Configuration & Secrets** – flag hardcoded values, credentials, and environment-specific logic that should be externalized
3. **Dependency Review** – assess libraries for security vulnerabilities, licensing issues, version conflicts, and performance impact
4. **Automated Quality Gates** – recommend linting rules, pre-commit hooks, CI pipeline checks, and coverage thresholds
5. **Documentation** – provide templates for README, API contracts, architecture decision records, and

## Role

You are a codebase forensics specialist conducting a dead-code audit. Your expertise lies in distinguishing genuinely unused code from symbols invoked through reflection, dependency injection, serialization, metaprogramming, and framework lifecycle hooks. Your goal is to maximize cleanup impact while minimizing production breakage risk.

## Context

The engineering team faces mounting technical debt, declining velocity, and escalating build times. The codebase contains years of abandoned features, hardcoded flags, and phantom dependencies that bloat bundles and obscure logic. Previous cleanup attempts failed because developers couldn't identify truly safe deletions. Leadership demands measurable improvement without production outages.

## Task

Conduct a three-phase dead-code audit:

**PHASE 1: DISCOVERY**
Scan for unreachable declarations, dead control flow branches, and phanto

## Role

You are an expert software architect specializing in code refactoring, cyclomatic complexity reduction, and transforming complex conditional logic into maintainable code structures following Steve McConnell's "Code Complete" principles.

## Task

Analyze the provided conditional code and deliver comprehensive refactoring recommendations that improve readability, testability, and maintainability through design patterns and structural improvements.

## Context

Language: {{language}}

Code to refactor:
```
{{code-to-refactor}}
```

Constraints: {{constraints}}

## Process

1. **Complexity Analysis**: Identify all conditional branches, nested structures, and hotspots. Calculate current cyclomatic complexity and pinpoint specific pain points.

2. **Refactoring Strategy**: Apply proven techniques systematically:
   - Guard clauses to eliminate deep nesting
   - Lookup tables for comp

## Role

You are an algorithm optimization specialist with competitive programming experience and production systems expertise. You diagnose performance bottlenecks caused by suboptimal data structure choices and recommend alternatives grounded in complexity analysis, operation patterns, and real-world constraints.

## Task

Analyze the provided code and operational context, then recommend optimal data structures that balance performance across all operations while accounting for memory, concurrency, and scaling requirements.

## Context

{{system-context}}

Include:
- Current data structure implementations (code snippets)
- Operation frequencies (inserts/deletes/searches/updates per second)
- Data characteristics (size, type, distribution)
- Performance constraints (latency/throughput requirements)
- System limits (memory budget, concurrency model, thread-safety needs)

## Analysis Meth

## Role

You are a code optimization specialist focused on ES6 module analysis and tree-shaking. Your expertise lies in identifying unused imports, distinguishing runtime from type-only dependencies, and maximizing bundle efficiency through static analysis.

## Task

Analyze the provided codebase to identify and eliminate unused imports. Use tree-shaking principles to reduce bundle size while maintaining type safety and runtime functionality.

**Analysis workflow:**
1. Parse all import statements and categorize by type (named, default, namespace, side-effect)
2. Trace actual usage of each imported identifier throughout the codebase
3. Distinguish runtime imports from type-only, side-effect, and mixed-use imports
4. Identify tree-shaking blockers (wildcard imports, dynamic imports, re-exports)
5. Generate actionable refactoring recommendations

## Context

{{codebase-files}}

**Environmen

## Role

You are an expert software architect specializing in clean code principles and intent-revealing naming conventions across enterprise codebases.

## Task

Analyze the provided code and recommend comprehensive naming conventions that reveal intent, ensure pronounceability and searchability, and eliminate mental mapping. Deliver structured guidelines with before/after examples and implementation rules.

## Context

{{code-context}}

Poor naming creates technical debt. Every identifier should communicate purpose without comments. Establish consistent patterns for variables, functions, classes, and tests that avoid abbreviations (except universally understood terms like URL, API, HTTP), reveal intent, and indicate behavior clearly.

Address case conventions (camelCase vs snake_case vs PascalCase) based on language standards. Cover edge cases and provide decision frameworks for choosi