Refactor Skills

Find and replace `any` types in TypeScript with precise types, generics, or `unknown` plus narrowing. Use when improving type safety, fixing implicit `any`, removing `any`, or migrating code to strict TypeScript.

Detect and resolve circular import chains that cause undefined values, runtime errors, or build/test warnings. Use when the user reports circular dependency warnings, undefined imports, or order-dependent test failures. Also trigger when shared imports suggest a dependency cycle.

Refactor classes or modules with too many responsibilities into smaller, cohesive units that follow the Single Responsibility Principle (SRP). Use when the user asks to split a god object, fat class, or bloated module, or when a file clearly handles multiple concerns.

Refactor long or multi-purpose functions into smaller, single-responsibility functions with clear names. Use when a function is large, complex, hard to read/test, or when the user asks to split, clean up, or reduce function complexity. Also trigger if pasted code contains an obviously large function.

Identify overly large or tightly coupled modules and split them into well-bounded units with clear public interfaces. Use when the user asks to reorganize modules, fix circular dependencies, separate concerns, or define module boundaries. Also trigger when shared code structure shows god modules, cross-cutting imports, or tight coupling.

Audit and refactor unclear, abbreviated, or misleading identifiers across a codebase, including variables, functions, parameters, files, and modules. Use this skill when the user asks to rename things, improve naming, audit identifiers, or fix cryptic names like `d`, `tmp`, `handleStuff`, or `doTheThing`. Also trigger for requests like "better names", "clearer code", or when poor naming likely causes readability issues.

Flatten deeply nested conditionals using guard clauses, early returns, or patterns like strategy, without changing behavior. Use when the user asks to simplify conditional logic, reduce nesting/indentation, or clean up “pyramid of doom” style code. Also trigger when pasted code shows 3+ levels of nesting.

Replace brittle snapshot tests with focused, meaningful assertions that verify behavior. Use when improving test reliability, fixing flaky tests, or migrating away from `toMatchSnapshot` / `toMatchInlineSnapshot`.

Specializes in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

Manage large-scale refactoring with Cascade coordination. Activate when users mention "large refactoring", "codebase migration", "architecture refactor", "major refactoring", or "system-wide changes". Handles complex refactoring operations. Use when working with windsurf refactoring large functionality. Trigger with phrases like "windsurf refactoring large", "windsurf large", "windsurf".