flutter-feature-based-clean-architecture
Feature-based clean architecture standards. ALWAYS consult when creating or modifying any file under lib/features/ — new features, domain entities, repositories, data sources, or screens. (triggers: lib/features/**, feature, domain, infrastructure, application, presentation)
Best use case
flutter-feature-based-clean-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Feature-based clean architecture standards. ALWAYS consult when creating or modifying any file under lib/features/ — new features, domain entities, repositories, data sources, or screens. (triggers: lib/features/**, feature, domain, infrastructure, application, presentation)
Teams using flutter-feature-based-clean-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flutter-feature-based-clean-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flutter-feature-based-clean-architecture Compares
| Feature / Agent | flutter-feature-based-clean-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Feature-based clean architecture standards. ALWAYS consult when creating or modifying any file under lib/features/ — new features, domain entities, repositories, data sources, or screens. (triggers: lib/features/**, feature, domain, infrastructure, application, presentation)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Feature-Based Clean Architecture ## **Priority: P0 (CRITICAL)** Standard for modular Clean Architecture organized by business features in `lib/features/`. ## Structure Every feature lives in `lib/features/` with **3-layer separation** (domain/data/presentation): - `domain/` — Entities, failures, and Repository interfaces. - `data/` — DTOs, DataSource, and Repository implementations. - `presentation/` — BLoC/Cubit, pages, and widgets. See [references/folder-structure.md](references/folder-structure.md) for the complete directory blueprint. ## Implementation Guidelines - **Feature Encapsulation**: Keep all logic, models, and UI internal to the feature directory (e.g., `lib/features/promotions/`). - **Strict Layering**: Maintain **domain/data/presentation** separation within each feature. - **Dependency Rule**: `Presentation -> Domain <- Data`. Domain must have zero external dependencies. - **Cross-Feature Communication**: Features only depend on the **Domain layer of other features**. Ensure there are **no cross-feature presentation or data imports**. - **Flat features**: Keep `lib/features/` flat; avoid nested features. - **No DTO Leakage**: Never expose DTOs or Data Sources to UI or other features; return Domain Entities. - **Shared logic**: Move **cross-cutting concerns** to `lib/shared/` or `lib/core/`. ## Reference & Examples For feature folder blueprints and cross-layer dependency templates: See [references/REFERENCE.md](references/REFERENCE.md). ## Anti-Patterns - ❌ `import '…/features/orders/data/models/order_dto.dart'` from another feature — only import Domain types across features - ❌ `lib/features/orders/domain/widgets/` — never put UI or Data classes inside Domain - ❌ `lib/features/orders/sub_orders/` — keep `lib/features/` flat; no nested feature directories - ❌ Calling another feature's repository directly from Presentation — route through that feature's BLoC or use-case ## Related Topics layer-based-clean-architecture | retrofit-networking | go-router-navigation | bloc-state-management | dependency-injection
Related Skills
anth-reference-architecture
Implement Claude API reference architectures for common use cases. Use when designing a Claude-powered application, choosing between direct API vs queue-based, or planning a multi-model architecture. Trigger with phrases like "anthropic architecture", "claude system design", "anthropic reference architecture", "design claude integration".
anth-architecture-variants
Choose and implement Claude API architecture patterns for different scales: serverless, microservice, event-driven, and edge deployment. Trigger with phrases like "anthropic architecture", "claude serverless", "claude microservice design", "edge claude deployment".
anima-reference-architecture
Implement reference architecture for Anima design-to-code automation. Use when designing a design system automation pipeline, structuring a Figma-to-React project, or planning team-scale design handoff. Trigger: "anima architecture", "design-to-code architecture", "anima project structure", "figma automation architecture".
algolia-reference-architecture
Implement Algolia reference architecture: index design, multi-index strategy, data pipeline, search service layer, and frontend/backend separation. Trigger: "algolia architecture", "algolia best practices", "algolia project structure", "how to organize algolia", "algolia index design".
alchemy-reference-architecture
Implement reference architecture for Alchemy-powered Web3 applications. Use when designing dApp infrastructure, planning multi-chain deployments, or structuring a production blockchain application. Trigger: "alchemy architecture", "dApp architecture", "alchemy project structure", "web3 system design", "alchemy multi-chain design".
adobe-reference-architecture
Implement Adobe reference architecture for production integrations covering Firefly Services, PDF Services, I/O Events, and App Builder with layered project layout, error boundaries, and health monitoring. Trigger with phrases like "adobe architecture", "adobe project structure", "how to organize adobe", "adobe layout", "adobe best practices".
adobe-architecture-variants
Choose and implement Adobe architecture blueprints: standalone SDK integration, Adobe App Builder serverless, and dedicated microservice with event-driven Firefly/PDF pipelines. Decision matrix based on team size and throughput. Trigger with phrases like "adobe architecture", "adobe blueprint", "adobe app builder vs standalone", "adobe microservice".
abridge-reference-architecture
Implement Abridge reference architecture for clinical AI integration. Use when designing a new Abridge deployment, reviewing project structure, or planning multi-site health system rollouts with EHR integration. Trigger: "abridge architecture", "abridge project structure", "abridge system design", "abridge multi-site".
git-branch-cleanup
Analyzes and safely cleans up local Git branches. Categorizes branches by merge status, staleness, and remote tracking. Provides interactive selection with safety guards. Use when the user wants to clean up branches, delete old branches, organize Git branches, or asks about which branches can be safely deleted.
gtm-partnership-architecture
Build and scale partner ecosystems that drive revenue and platform adoption. Use when building partner programs from scratch, tiering partnerships, managing co-marketing, making build-vs-partner decisions, or structuring crawl-walk-run partner deployment.
create-github-issues-feature-from-implementation-plan
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
create-github-issue-feature-from-specification
Create GitHub Issue for feature request from specification file using feature_request.yml template.