Mobile-first Clean Architecture and Domain Driven Design for Flutter apps. Repository pattern, use case layer, dependency injection (GetIt/Injectable), error handling (Either/Failure), feature-sliced project structure, and test strategy.
SkillScore77Maintained
Automatic
◆Coding pack
Last verified 8/6/2026
What it changes
Passed 17 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill77%
Checks it passed that the model alone missed
The entity class extends Equatable
The UseCase returns an Either type
Use cases are limited to a maximum of 50 lines
and 9 more in the full report
9 fixed8 passed either way5 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+107%
Agent turns
0%
Response time
-18%
Model gemini-3.6-flashMeasured 8/6/2026v117 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
I'm reviewing code limits for our team's Flutter architecture guidelines. What are the maximum line count rules for widgets/screens, repository implementations, and use cases?
What was checked, without and with the skill
Checked
Without skill
With skill
Widgets and screens are limited to a maximum of 200 lines
Passed
Passed
Repository implementations are limited to a maximum of 150 lines
Missed
Passed
Use cases are limited to a maximum of 50 lines
Missed
Passed
case-10 · gemini-3.6-flash · 8/6/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md439 linessingle file
Mobile Architecture — Clean Architecture for Flutter
Testable, maintainable Flutter applications built on SOLID principles,
DDD, and a mobile-first mindset.
Layered Architecture
┌─────────────────────────────────────────────────────┐
│ PRESENTATION LAYER │
│ Screens → Widgets → BLoC/Cubit/Provider │
│ (UI state management, user interactions) │
├─────────────────────────────────────────────────────┤
│ DOMAIN LAYER │
│ Entities → Use Cases → Repository Interfaces │
│ (Business logic — platform independent) │
├─────────────────────────────────────────────────────┤
│ DATA LAYER │
│ Models → Repository Implementations → Data Sources │
│ (API, local DB, cache) │
└─────────────────────────────────────────────────────┘
DEPENDENCY DIRECTION: Presentation → Domain ← Data
The Domain layer depends on nothing.