agentsclimarketplace
Sign in

Clean architecture

Skill amadeus-dlc/amadeus/amadeus/spaces/default/knowledge/amadeus-shared/software-design/clean-architecture

Use only when the user explicitly asks for Clean Architecture design, implementation, or review. Applies a domain, use case, interface adapter, and infrastructure layer model, with persistence and RPC adapters outside the domain and use-case rules. Do not trigger for generic architecture advice, hexagonal architecture, onion architecture, or ordinary design review unless Clean Architecture is named.From its SKILL.md

Install
npx -y skills add amadeus-dlc/amadeus --skill clean-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 290 tokens by cl100k_base, as published. Nobody here has run it

Clean Architecture

Use this skill only for projects that intentionally follow Clean Architecture. Keep policy inward and mechanisms outward.

Layer Rule

  • Domain: entities, value objects, aggregates, domain services, domain events, and invariants.

  • Use cases: application-specific orchestration, transaction boundaries, ports, authorization decisions that are application policy, and repository interface usage.

  • Interface adapters: controllers, presenters, gateways, repository implementations, RPC adapters, DTO mapping, and persistence mapping.

  • Infrastructure: cross-cutting mechanisms such as logging, configuration, metrics, DI wiring, clocks, IDs, and concrete driver setup.

Workflow

  1. Confirm the project actually uses Clean Architecture.

  2. Map the touched code to the four layers.

  3. Check dependency direction: outer layers may depend inward; inward layers must not know outer mechanisms.

  4. Move persistence, RPC, UI, and framework details out of domain and use-case code.

  5. Report the minimal relocation or interface extraction needed.

Reference

Read references/layer-responsibilities.md when placement is ambiguous.

Detailed Reference

For non-trivial implementation, review, or refactoring work, read references/details.md before giving final guidance. It contains the detailed rules, examples, smells, and migration notes that do not belong in the short invocation body.

Output

Provide a layer-by-layer finding list, dependency violations, and concrete file-placement recommendations.

What ships with it: 2 files

2.7 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most architecture codebase skills give in 290 tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-07

  • Ask the user which candidate to explorein 45 of 811, across 15 files
  • Apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • Read any relevant architecture decision records firstin 31 of 811, across 8 files
  • Use exact glossary terms in every suggestionin 30 of 811, across 10 files
  • Accept dependencies instead of creating themin 24 of 811, across 5 files
  • Include before and after visualisations for each candidatein 24 of 811, across 5 files
  • Read the domain glossary before exploringin 24 of 811, across 6 files
  • Return results instead of producing side effectsin 23 of 811, across 4 files
  • Explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • Introduce seams only where things varyin 22 of 811, across 3 files
  • Reduce the number of methodsin 21 of 811, across 2 files
  • Design deep modules with small interfacesin 21 of 811, across 3 files

Said here and by no other author read

  • keep policy inward and mechanisms outward
  • confirm the project uses clean architecture
  • map touched code to the four layers
  • move persistence and rpc details outward
  • report minimal relocations needed
  • read layer responsibilities reference when placement is ambiguous

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,834. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.