Clean Architecture (any stack, adapts to the project)

Implement features with Clean Architecture — dependency direction frameworks & drivers → adapters → use cases → domain — in whatever stack and idiom the project already uses: mobile app, web frontend, backend service, or desktop. The skill imposes boundaries, never tools: packages, naming, and state management are detected from the project, not chosen by the skill.

This file is a router. You must open and follow the reference each step links — never work from memory of it.

Not this skill: pure visual tweaks with no data or business change; finding the root cause of a defect, or deciding where an already-understood fix belongs; documentation-only work; comparing an implementation against a design file.

The two iron rules