Flutter Cross Master is a skill published by agensi that guides developers through building production-grade Flutter applications from initial project structure through to App Store deployment. It specializes in implementing Clean Architecture with distinct Presentation, Domain, and Data layers, keeping concerns separated and codebases maintainable over the long term.

For state management, the skill applies the BLoC (Business Logic Component) pattern. It incorporates Domain-Driven Design concepts including standardized DTOs, Value Objects, and Auth Facades to prevent the tightly-coupled code that often results from ad-hoc AI generation. Dependency injection is handled through get_it, and the skill enforces Test-Driven Development practices throughout.

Testing support spans Unit, Widget, and native UI testing using the Patrol framework, all structured around the Arrange-Act-Assert pattern. Error handling follows functional programming conventions using Either types in Dart. Native platform integrations—such as payment flows or hardware sensor access—are addressed via MethodChannels and Platform Channels.

Code output makes use of Dart 3 features including Records and Pattern Matching. The skill is suited for teams that need generated Flutter code to conform to established architectural standards rather than producing exploratory or prototype-quality output.

This is a skill, not an MCP server, so it carries no runtime transport, tool list, or environment variables.

Use cases

Scaffold a Flutter project with Clean Architecture layers already separated

Generate BLoC state management boilerplate for a new feature

Produce unit and widget test files following the Arrange-Act-Assert pattern

Implement native platform integrations using MethodChannels for payments or sensors

Set up dependency injection configuration with get_it

Add Either-based error handling to a Dart domain layer

When to use it

Building a Flutter app that must remain maintainable across multiple team members

Projects requiring strict architectural boundaries between UI, domain, and data layers

When TDD and testable code are non-negotiable requirements

Integrating native platform features via MethodChannels or Platform Channels

Flutter Cross Master

Use cases

When to use it

When not to use it