refactoring▌

Java method extraction refactoring for improved readability and maintainability. \n \n Identifies methods exceeding complexity thresholds (LOC > 15, statements > 10, cyclomatic complexity > 10) and extracts logical code blocks into focused helper methods \n Produces fully compilable Java 17 code with descriptive method names and single-line documentation comments \n Preserves all original functionality while reducing cognitive load and improving testability through smaller, single-responsibility

Audit and fix visual hierarchy, spacing, color, and depth in web UIs using systematic design principles. \n \n Seven core principles: visual hierarchy through size/weight/color, constrained spacing scales (4/8/16/24/32/48/64px), modular typography, systematic color palettes with 5-9 shades per color, shadow elevation scales, deliberate image/icon sizing, and intentional layout composition \n Design in grayscale first, add color last; rate designs 0-10 against framework guidelines with specific i

Refactor code while preserving behavior, improving clarity, and reducing complexity. \n \n Covers five core refactoring patterns: Extract Method, DRY principle removal, conditional-to-polymorphism conversion, parameter object introduction, and SOLID principle application \n Includes behavior validation workflow with pre-refactoring analysis, post-refactoring testing (unit, type, lint, snapshot), and change documentation \n Provides refactoring checklist covering function length, parameter count,

If "Index is stale" → run npx gitnexus analyze in terminal.

Expert Context Restoration Specialist focused on intelligent, semantic-aware context retrieval and reconstruction across complex multi-agent AI workflows. Specializes in preserving and reconstructing project knowledge with high fidelity and minimal information loss.

Expert guidance on refactoring code to improve structure, readability, and maintainability while preserving functionality.

You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.

A disciplined approach to improving the internal structure of existing code without changing its observable behavior. Apply these named transformations when reviewing code, reducing technical debt, or preparing code for new features. Every refactoring follows the same loop: verify tests pass, apply one small structural change, verify tests still pass.

Code refactoring expert applying clean code principles, SOLID patterns, and best practices to improve maintainability. \n \n Analyzes code smells, dependencies, and risky hotspots to identify refactoring priorities \n Proposes incremental refactor plans with small, reviewable slices that preserve existing behavior \n Covers duplication reduction, complexity simplification, testability improvements, and design consistency \n Includes test updates and regression verification to ensure safe, non-br

Structured patterns and techniques for improving code quality through safe, behavior-preserving refactoring. \n \n Covers common code smells including long methods, deeply nested conditionals, primitive obsession, and feature envy with before/after examples \n Provides core refactoring techniques: extract method, replace conditional with polymorphism, introduce parameter objects, and replace magic numbers with constants \n Emphasizes safe refactoring workflow: ensure test coverage first, make sm