rule-flutter-flutter-architecture-always-on
OfficialEnforce Flutter architecture across tasks.
Software Engineering#architecture#routing#state-management#flutter#dependency-injection#module-ownership
Authorbelluga
Version1.0.0
Installs0
System Documentation
What problem does it solve?
Flutter projects often drift from architectural tenets, leading to tangled widgets, unclear state ownership, and brittle routing. This Rule enforces clear separation of concerns and governance across the Flutter client.
Core Features & Use Cases
- Enforces widget purity by ensuring controllers own all state and orchestration; widgets remain presentation-only.
- enforces DI/ownership boundaries and route governance with AutoRoute and guarded navigation.
- Use Case: In a new feature module, the rule ensures that a screen's state is managed by a controller and that navigation uses AutoRoute with proper guards, preventing ad-hoc Navigator usage.
Quick Start
Apply this rule to every Flutter feature to ensure architectural consistency and prevent scope creep.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: rule-flutter-flutter-architecture-always-on Download link: https://github.com/belluga/delphi-ai/archive/main.zip#rule-flutter-flutter-architecture-always-on Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.