skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
thienqo/flutter-skills124 installs

flutter-architecture

Select, review, or evolve Flutter application boundaries, dependency direction, and feature organization. Use for new project structure, scaling problems, or architecture migrations; do not impose a new pattern during a focused feature fix.

How do I install this agent skill?

npx skills add https://github.com/thienqo/flutter-skills --skill flutter-architecture
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill provides architectural guidance and best practices for Flutter application development. It contains only documentation and references to official Flutter resources. No executable code, script dependencies, or security risks were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Flutter Architecture

Choose the least complex architecture that keeps responsibilities clear, state testable, and dependencies replaceable.

Preserve before migrating

Inspect the existing feature structure, state mechanism, dependency injection, data sources, tests, and team conventions. Extend a coherent architecture even when it differs from a preferred example. Propose migration only for a concrete problem and make it incremental.

Baseline boundaries

  • Views render state and forward user intent; keep data access and business rules outside widgets.
  • Presentation logic owns UI state and commands.
  • Repositories are the source of truth for domain data and coordinate services or caches.
  • Services wrap external systems such as HTTP, storage, and platform plugins.
  • Add use cases/domain services only when logic is reused, complex, or otherwise clutters presentation state.
  • Point dependencies inward through explicit interfaces where replacement or testing justifies them.

The Flutter team's MVVM guidance is a useful default for a new scalable application, not a mandate to replace Riverpod, Bloc, Redux, or an established feature-first design.

Organization

Prefer user-facing feature boundaries. Place genuinely shared infrastructure in a small core area. Avoid global folders that accumulate unrelated models, widgets, and helpers.

Load greenfield and evolution for new-project choices or incremental migrations. Load feature boundaries and dependency rules when modules leak across features or ownership is unclear.

Verification

Demonstrate the dependency path for one feature, test presentation logic without rendering widgets where practical, and confirm no circular or UI-to-infrastructure shortcuts were introduced.

Sources

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/thienqo/flutter-skills/flutter-architecture">View flutter-architecture on skillZs</a>