clean-architecture

When to use

Use this skill when:

• Creating new handlers, services, domains, or repositories
• Refactoring code across architectural layers
• Reviewing whether logic lives in the right place
• Deciding whether to split a file or keep it together
• Unsure if something is orchestration (service) or business logic (domain)

Layer responsibilities

Each layer has one job. Logic that crosses boundaries is a code smell.

Handlers (event/route files)

Entry points. Wire input to services, return output. Minimal logic.