About clean-architecture
A skill for applying Clean Architecture to application development, with guidance for Flutter and Go projects. It emphasizes inward dependencies, separated layers, testable interfaces, and focused business logic.
Key features
- 01Domain, application, infrastructure, and presentation layers
- 02Flutter feature-first project organization
- 03flutter_bloc state management patterns
- 04Go backend handlers, services, and repositories
- 05Interface-driven testing and dependency injection
Use cases
- 01Structuring a Flutter application by feature
- 02Separating Go business logic from data access
- 03Designing dependency boundaries between layers
- 04Writing unit tests with mocks
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ mindrally/ skills --skill clean-architectureAfter installing, type/clean-architecturein Claude Code to confirm it loaded.
Details
From the project READMEClean Architecture
You are an expert in Clean Architecture patterns for application development.
Core Principles
Clean Architecture enforces separation of concerns through distinct layers with dependencies pointing inward:
- Domain Layer (innermost) - Business logic and entities
- Application Layer - Use cases and application-specific logic
- Infrastructure Layer - External concerns (databases, APIs, frameworks)
- Presentation Layer (outermost) - UI and user interaction
The fundamental rule: inner layers must never depend on outer layers.
Flutter + Clean Architecture
Architecture Layers
- Presentation: Widgets, BLoCs, and UI components
- Domain: Entities, use cases, and repository interfaces
- Data: Repository implementations, data sources, and models
Feature-first Organization
feature/
data/
datasources/
models/
repositories/
domain/
entities/
repositories/
usecases/
presentation/
bloc/
pages/
widgets/
State Management with flutter_bloc
- Use flutter_bloc for state management
- Implement immutable states via Freezed
- Handle events and states with proper patterns
- Keep BLoCs focused on single responsibilities
Error Handling
- Implement Either<Failure, Success> pattern from Dartz
- Use functional error handling without exceptions
- Define clear Failure types for different error scenarios
Key Libraries
flutter_bloc- State managementfreezed- Immutable classes and unionsget_it- Service locator for DIdartz- Functional programming utilities
Go Backend Clean Architecture
Layer Separation
- Handlers - HTTP/gRPC request handling
- Services - Business logic and use cases
- Repositories - Data access abstractions
- Domain Models - Core business entities
Interface-driven Development
- Define interfaces for all dependencies
- Implement dependency injection through constructors
- Keep interfaces small and focused
- Allow easy mocking for tests
Project Structure
project/
cmd/ # Application entry points
internal/
domain/ # Business entities and interfaces
service/ # Business logic implementation
repository/ # Data access implementation
handler/ # HTTP/gRPC handlers
pkg/ # Shared utilities
Testing Strategy
- Write table-driven unit tests with mocks
- Separate fast unit tests from integration tests
- Use interfaces to inject test doubles
- Achieve high coverage of business logic
Comments
Markdown supported