ajianaz/skills-collection/flutter-enterprise
Claude Code and agent skill by ajianaz/skills-collection
- community
Checking that the SKILL.md file is still in the repository.
Lightweight Flutter enterprise development skill focused on feature-based clean architecture. Use when user asks to: (1) Build enterprise Flutter apps with clean architecture, (2) Implement feature-based modular structure, (3) Set up scalable Flutter project organization, (4) Create maintainable enterprise codebase. Triggers: Flutter enterprise app, clean architecture Flutter, feature-based Flutter, enterprise Flutter structure, modular Flutter architecture
Install
npx vskill@latest install ajianaz/skills-collection/flutter-enterpriseSKILL.md
Flutter Enterprise - Feature-Based Clean Architecture
Lightweight Flutter development skill for building enterprise applications using feature-based clean architecture patterns.
Core Philosophy
"Feature-first, testable, maintainable enterprise code" - Focus on:
| Priority | Area | Purpose | |
|---|---|---|---|
| 1 | Feature-Based Structure | Modular, scalable code organization | |
| 2 | Clean Architecture | Separation of concerns and testability | |
| 3 | Dependency Injection | Loose coupling and maintainability | |
| 4 | Enterprise Patterns | Proven enterprise development practices | |
| 5 | Code Generation | Boilerplate reduction and consistency |
Development Workflow
Execute phases sequentially. Complete each before proceeding.
Phase 1: Analyze Requirements
- Feature identification - Identify distinct business features
- Data flow analysis - Map data dependencies between features
- Integration points - Define external service integrations
- Scalability requirements - Plan for future feature additions
Output: Feature breakdown with dependency mapping.
Phase 2: Design Feature Architecture
- Feature boundary definition - Define clear feature boundaries
- Data layer planning - Design repositories and data sources
- Domain modeling - Create entities and use cases
- Presentation layer design - Plan UI components and state management
Output: Feature architecture diagram and data contracts.
Phase 3: Implement Core Structure
- Project setup - Create feature-based directory structure
- Dependency injection - Set up service locator or DI container
- Core utilities - Create shared utilities and constants
- Navigation setup - Implement routing structure
Feature Structure Pattern:
Phase 4: Implement Feature Modules
- Data layer - Implement repositories and data sources
- Domain layer - Create business logic and use cases
- Presentation layer - Build UI components and state management
- Feature integration - Connect feature to main app
Clean Architecture Implementation:
Phase 5: Setup Testing Structure
- Unit tests - Test domain layer and use cases
- Integration tests - Test data layer and repositories
- Widget tests - Test presentation layer components
- Test utilities - Create mock objects and test helpers
Quick Reference
Feature-Based Architecture Patterns
| Layer | Responsibility | Key Components | |
|---|---|---|---|
| Presentation | UI and State Management | Pages, Widgets, Providers/Bloc | |
| Domain | Business Logic | Entities, Use Cases, Repository Interfaces | |
| Data | Data Implementation | Models, Data Sources, Repository Implementations |
Dependency Injection Setup
State Management Patterns
This skill now supports state management neutrality with equivalent implementations for all four major approaches:
Provider Pattern
Bloc Pattern
Riverpod Pattern
GetX Pattern
Resources
- Architecture patterns: See
references/clean-architecture.md - Feature templates: See
references/feature-templates.md - Testing patterns: See
references/testing-patterns.md - Code generation: See
references/code-generation.md
Technical Stack
- Architecture: Clean Architecture with feature-based structure
- State Management: Provider/Bloc/Riverpod/GetX (state management neutral - all four approaches fully supported with equivalent examples)
- Dependency Injection: GetIt/Injectable
- Code Generation: build_runner, json_annotation, freezed
- Testing: mockito, bloc_test, widget testing
Best Practices
- Feature Independence: Each feature should be self-contained
- Dependency Rule: Dependencies point inward (Presentation → Domain ← Data)
- Interface Segregation: Keep interfaces small and focused
- Single Responsibility: Each class has one reason to change
- Test Coverage: Aim for 80%+ coverage on domain and data layers
This Flutter enterprise skill transforms complex enterprise app development into a systematic process that ensures maintainable, scalable, and testable applications using feature-based clean architecture.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/flutter-enterprise/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 3
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 21 Apr 2026, 6 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/ajianaz/skills-collection/flutter-enterprise)