Clean architecture

Skill VRIL-LABS/skill-jam/skills/ai-ml/skills-main-2/skills-main/clean-architecture

Guidelines for implementing Clean Architecture patterns in Flutter and Go applications, with emphasis on separation of concerns, dependency rules, and testability.From its SKILL.md

Install

npx -y skills add VRIL-LABS/skill-jam --skill clean-architecture

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 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.7 KB, 526 tokens by cl100k_base, as published. Nobody here has run it

Clean 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 management
freezed - Immutable classes and unions
get_it - Service locator for DI
dartz - 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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

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

Counted across 858 of the 1,304 authors here whose files we hold, read 2026-09-06

Apply the deletion test to identify shallow modulesin 32 of 858, across 31 files
Read domain glossary and ADRs before exploringin 22 of 858, across 19 files
Use Tailwind and Mermaid via CDN for reportsin 21 of 858, across 18 files
Document architecture decision recordsin 20 of 858, across 12 files
Offer to record ADRs for rejected candidatesin 17 of 858, across 14 files
Limit primary navigation to four to seven itemsin 17 of 858, across 7 files
Write HTML report to the system temp directoryin 17 of 858, across 14 files
Read product marketing context before asking questionsin 16 of 858, across 6 files
Use Mermaid graph TD for visual sitemapsin 15 of 858, across 5 files
Ensure every page has at least one internal linkin 15 of 858, across 5 files
Use ASCII tree format for page hierarchy draftsin 15 of 858, across 5 files
Enforce lowercase URLs with hyphensin 15 of 858, across 5 files

Said here and by no other author read

Ensure inner layers never depend on outer layers
Use immutable states for state management
Keep interfaces small and focused
Write table-driven unit tests
Inject test doubles using interfaces

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.