flutter-mail-project-architecture
Defines and manages structure for Flutter projects.
Install
mkdir -p .claude/skills/flutter-mail-project-architecture && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16549" && unzip -o skill.zip -d .claude/skills/flutter-mail-project-architecture && rm skill.zipInstalls to .claude/skills/flutter-mail-project-architecture
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when planning, scaffolding, or refactoring the overall Flutter Inbox One project structure in this repository, especially when deciding file placement, MVC boundaries, routing/theme foundations, or stage order. Do not use for isolated single-layer edits that clearly belong only to models, services, controllers, or views.Key capabilities
- →Plan Flutter Inbox One project structure
- →Scaffold new features within MVC boundaries
- →Refactor existing MVC layers
- →Decide file placement for models, services, controllers, views
- →Establish routing and theme foundations
How it works
The skill guides the planning, scaffolding, or refactoring of the Flutter Inbox One project structure, ensuring adherence to MVC boundaries and proper file placement.
Inputs & outputs
When to use flutter-mail-project-architecture
- →Planning project structure
- →Scaffolding new features
- →Refactoring MVC layers
About this skill
Flutter Mail Project Architecture
Read first
dev/PRD.mddev/TDD.mddev/DELIVERY_PLAN.md- Root
AGENTS.md - The closest nested
AGENTS.mdfor the directories you touch
Core architecture
- This repository follows an MVC-style Flutter structure:
lib/modelslib/serviceslib/controllerslib/viewslib/other
- Keep cross-layer responsibilities clean:
- models define data shapes
- services talk to APIs/local storage
- controllers own state and actions
- views render UI
- other contains router/theme/utils/constants
Delivery order
- Respect the staged flow in
dev/DELIVERY_PLAN.md. - Prefer this order unless the user explicitly reprioritizes:
- Foundation
- Inbox Parity
- Action & AI Completion
Structural decisions
- Preserve document-defined folder names and boundaries unless the docs are intentionally updated.
- If a request would mix multiple responsibilities into one layer, split the work before coding.
- When introducing shared logic, place it in the narrowest stable layer instead of leaking it upward into views or downward into models.
Output expectations
- When you make structural changes, mention which stage the work belongs to.
- Call out any doc conflict before silently diverging from the PRD/TDD.
When not to use it
- →For isolated single-layer edits that clearly belong only to models
- →For isolated single-layer edits that clearly belong only to services
- →For isolated single-layer edits that clearly belong only to controllers or views
Limitations
- →Does not handle isolated single-layer edits
- →Requires adherence to MVC-style Flutter structure
- →Preserves document-defined folder names and boundaries
How it compares
This skill enforces a consistent MVC architecture for Flutter projects, preventing structural inconsistencies and ensuring clear separation of concerns that might be overlooked in unguided development.
Compared to similar skills
flutter-mail-project-architecture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| flutter-mail-project-architecture (this skill) | 0 | 4mo | No flags | Intermediate |
| mobile-state-management-patterns | 0 | 4mo | No flags | Intermediate |
| flutter-development | 1,555 | 5mo | No flags | Intermediate |
| flutter-expert | 73 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by minchanpark
View all by minchanpark →You might also like
mobile-state-management-patterns
almasumdev
Comparison of mobile state management patterns (MVVM, MVI, TEA, Redux, BLoC, Observable, Compose state, SwiftUI state) and how to choose. Use when designing state flow or evaluating a state library.
flutter-development
aj-geddes
Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.
flutter-expert
sickn33
Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.
flutter
alinaqi
Flutter development with Riverpod state management, Freezed, go_router, and mocktail testing
flutter-architecture-expert
flutter-it
Architecture guidance for Flutter apps using the flutter_it construction set (get_it, watch_it, command_it, listen_it). Covers Pragmatic Flutter Architecture (PFA) with Services/Managers/Views, feature-based project structure, manager pattern, proxy pattern with optimistic updates and override fields, DataRepository with reference counting, scoped services, widget granularity, testing, and best practices. Use when designing app architecture, structuring Flutter projects, implementing managers or proxies, or planning feature organization.
mobile-developer
sickn33
Develop React Native, Flutter, or native mobile apps with modern architecture patterns. Masters cross-platform development, native integrations, offline sync, and app store optimization. Use PROACTIVELY for mobile features, cross-platform code, or app optimization.