clean-code-architecture-skill-pack

Turn feature requests and product requirements into clean-architecture-aligned design and implementation by clarifying acceptance criteria, modeling domain concepts and use cases, defining ports and adapters, and writing new code with business rules isolated from frameworks. Use when the request is about requirement analysis, feature breakdown, domain modeling, use-case design, port and adapter design, acceptance criteria, API or service design, application flow design, or implementing new behavior from a spec rather than cleaning up legacy code. Typical triggers include requests such as "analyze this requirement", "break this feature into use cases", "design ports and adapters", and "implement this spec cleanly". Do not use as the primary skill when the main job is diagnosing and refactoring an already-working legacy implementation.

Provide the shared philosophy, decision rules, and quality bar behind clean-code and clean-architecture work. Use when the task is about common principles, tradeoffs, boundary decisions, refactor-versus-redesign judgment, architecture quality standards, or coordinating routing, refactoring, and requirements-driven implementation under one consistent approach.

Diagnose and improve existing code through a clean-code and clean-architecture lens by identifying code smells, boundary violations, naming problems, oversized functions or classes, tangled dependencies, hidden side effects, and missing safety nets, then applying safe refactoring. Use when the request is about legacy code review, code quality diagnosis, structural cleanup, refactoring, dependency untangling, responsibility splitting, complexity reduction, readability improvement, testability improvement, maintainability improvement, or cleaning up existing behavior without intentionally adding new product features. Typical triggers include requests such as "why is this code so hard to change?", "separate responsibilities", "this function is too long", "the dependencies are tangled", and "keep the behavior the same and only improve the structure". Do not use as the primary skill when the main job is implementing a new feature from a requirement.

Route ambiguous or mixed clean-code and clean-architecture requests to the right workflow. Use when the user mentions clean code, clean architecture, structural improvement, design quality, refactoring, requirement analysis, ports and adapters, maintainability, or architecture, but it is not yet clear whether the main job is diagnosing existing code, implementing new behavior from requirements, or splitting the task into both phases. Typical triggers include requests such as "is this a refactor or a redesign?", "we need a new feature but the current code is a mess", and "which workflow should we use first?"