Clean Code and Architecture

The problem

Legacy codebases often suffer from tangled dependencies and brittle logic that makes every new feature a struggle. Most AI-generated code treats "it works" as the finish line, ignoring the structural integrity needed for long-term maintenance.

What it does

• Enforces the Dependency Rule to ensure core business logic remains independent of frameworks, databases, and UIs.
• Refactors functions and classes to follow SOLID principles, ensuring single responsibility and proper abstraction levels.
• Wraps third-party APIs behind local adapters to prevent vendor lock-in and simplify testing.
• Implements a F.I.R.S.T. compliant testing strategy where business rules are validated without infrastructure dependencies.
• Identifies and removes code smells using a systematic checklist for naming, error handling, and concurrency.

Why this beats prompting it yourself

Standard prompts often produce "good enough" code that fails under architectural scrutiny. This skill uses a modular reference system to apply specific Martin-standard rules without token bloat, ensuring your agent follows a strict, behavior-preserving refactoring workflow.

Use cases

• Decoupling a bloated controller from a specific database ORM.
• Performing an automated code review on a pull request to catch structural smells.
• Extracting business logic into pure entities that are testable without a runtime.
• Wrapping a messy third-party library to stabilize your internal API.

Known limitations

Requires an existing test suite to ensure behavior-preserving micro-steps. Works best when the agent has access to the full project file tree for dependency mapping.