clean-architecture
Skill0 starsChanged 4 days agoMITView on GitHub
Which code goes in domain/, data/, presentation/ and ai/, which way imports may point, and where a new file belongs. Use when adding a file, adding a repository, or when an import is rejected by the layer rules.
30 other projects use a version of this.
Adopted by
Most recently taken up by
- tiagosilva07/zyrax-guardtheir own version, first seen Nov 15, 2026
- kinhluan/skillstheir own version, first seen Nov 8, 2026
- codewithmukesh/dotnet-claude-kittheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- zdanovichnick/dotnet-pilottheir own version, first seen Nov 6, 2026
- nledford/engineering-review-boardtheir own version, first seen Nov 3, 2026
Used with
Projects with it also use convention-learner, opentelemetry and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
codewithmukeshSkillconvention-learner
Detects and enforces project-specific coding conventions by analyzing existing codebase patterns. Learns naming conventions, folder structure, test organization, and coding style from the existing code. Load when: "conventions", "coding standards", "project patterns", "enforce style", "detect patterns", "learn conventions", "code consistency".
Also in 3 projects that use this
- codewithmukeshSkill
opentelemetry
OpenTelemetry observability for .NET 10 applications. Covers traces, metrics, and logs using the OpenTelemetry SDK with OTLP export. Includes custom ActivitySource, IMeterFactory metrics, resource configuration, and Aspire Dashboard integration. Load this skill when setting up distributed tracing, custom metrics, OTLP export, or when the user mentions "OpenTelemetry", "OTLP", "traces", "spans", "Activity", "ActivitySource", "metrics", "IMeterFactory", "Meter", "Counter", "Histogram", "Gauge", "telemetry", "observability", "distributed tracing", "OTEL", or "Aspire Dashboard".
Also in 3 projects that use this
MovGP0Skillmodern-csharp
Modern C# style guidance for Bendex and MicroSea code changes, including primary constructors, expression-bodied members, var usage, target-typed new, lambdas, and pattern matching.
Also in 3 projects that use this
MicrosoftSkillresilience
Apply resilience patterns (retry, backoff, circuit breaking) when writing or reviewing code that makes outbound HTTP/REST calls, database operations, or any I/O that can experience transient failures. Use this skill when: (1) writing new code that calls external services or APIs, (2) reviewing code that uses fetch, HTTP clients, or service-to-service calls, (3) adding queue consumers or workers that interact with remote systems, (4) debugging intermittent failures in production.
Also in 3 projects that use this
hongyuancSkillvertical-slice
Build and evaluate a production-quality vertical slice before advancing from Pre-Production to Production.
Also in 3 projects that use this
wpankSkillcaching
Caching strategies, invalidation, eviction policies, HTTP caching, distributed caching, and anti-patterns. Use when designing cache layers, choosing eviction policies, debugging stale data, or optimizing read-heavy workloads.
Also in 3 projects that use this
Other versions30 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 30
- ciembor/agent-rules-books★ 2.8ksame name
- wondelai/skills★ 2.6ksame name
- codewithmukesh/dotnet-claude-kit★ 808same name
- Mindrally/skills★ 275same name
- Resgrid/Core★ 238same name
- GabrielMartinMoran/mind★ 193same name
- tokenaissance/clean-architecture★ 17same name
- G1Joshi/Agent-Skills★ 15same name
- korallis/skills-collection★ 14same name
- nledford/engineering-review-board★ 11same name
20 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibilitySkill
- actionsSkill
- adding-a-featureSkill
- agent-workflowSkill
- app-contextSkill
- approval-and-safetySkill
- backend-proxySkill
- background-workSkill
- build-an-appSkill
- capture-learningsSkill
- customizing-the-assistantSkill
- delegate-to-agentSkill
- edit-boundariesSkill
- i18n-and-rtlSkill
- model-providersSkill
- performanceSkill
- permissions-and-platformSkill
- read-the-docsSkill
- reliable-mutationsSkill
- routingSkill
- secretsSkill
- state-managementSkill
- storing-dataSkill
- testingSkill
- ui-designSkill
- upgrade-the-frameworkSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Don't load this for how screens refresh or hold state.
- Very specific: line 43
Write the interface in lib/domain/repositories/.
- Very specific: line 46
Read it in a provider with ServiceLocator.getIt<ItemsRepository>(), typed as the interface (see …
“Common” is measured: kept by at least 6 in 10 of the 28 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clean architecture
Don't load this for how screens refresh or hold state; see state-management.
Rule
Imports point inward, toward lib/domain/:
lib/domain/imports neitherdata/,presentation/nor Flutter (package:flutter/…,dart:ui). It is plain Dart.lib/presentation/imports nothing fromdata/. It reaches data through a repository interface fromlib/domain/repositories/and changes data through an action.lib/data/implements the domain interfaces.lib/ai/holds the adapters between the app and the assistant.
Enforced by the lint rules domain_layer_boundaries and presentation_layer_boundaries. They show only in dart analyze run from the repo root (and in tool/check.sh), not in flutter analyze.
Why
Plain-Dart domain/ is why the same actions run in the app, in tests and in the action CLI (tool/action.dart). If domain/ knew about Drift or widgets, the CLI and the assistant could not use it.
How
Where a new file goes:
| You are adding | Put it in |
| An entity (a plain value class) | lib/domain/entities/, like lib/domain/entities/item.dart |
| A repository interface | lib/domain/repositories/, like lib/domain/repositories/items_repository.dart |
| An action | lib/domain/actions/, registered in lib/domain/actions/app_actions.dart |
| A Drift table or DAO | lib/data/local/database/tables/ or .../daos/ |
| A repository implementation | lib/data/repositories/, like lib/data/repositories/drift_items_repository.dart |
| A screen or widget | lib/presentation/<feature>/ |
| A Riverpod provider | lib/presentation/providers/ |
| Theme tokens, shared state widgets | lib/core/ |
| Screen summaries, router and change-event adapters | lib/ai/ |
Steps for new data:
- Write the interface in
lib/domain/repositories/. Name readswatch…orget…. - Implement it in
lib/data/repositories/. Map table rows to entities there, as_toItemdoes inDriftItemsRepository. - Register the implementation against the interface in
lib/data/di/data_layer_injection.dart. - Read it in a provider with
ServiceLocator.getIt<ItemsRepository>(), typed as the interface (seelib/presentation/providers/items_provider.dart).
Anti-patterns
- A screen importing
lib/data/…or a Drift class. Add an interface member instead. - A domain file importing
package:flutter/material.dartfor oneColor. Keep the value as plain data and convert inpresentation/. - Putting model calls or widgets in an action.
- Using
// ignore: flutter_agentify_lints/domain_layer_boundariesto get past an import. The doctor's ratchet counts ignores and they may only go down. - Exposing a Drift row type from a repository interface. Return entities.
Verification
dart analyze --fatal-infosfrom the repo root reports a boundary violation asdomain_layer_boundariesorpresentation_layer_boundaries.tool/check.shruns it with the tests and ends withAll checks passed.
Related skills
state-management— providers and refresh after writes.storing-data— the tables and migrations behind a data-layer repository.actions— writing the action that changes the data.adding-a-feature— the whole path from screen to screen-context entry.testing— which layer each kind of test covers.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.