flutter-architecture-adherence

Name: flutter-architecture-adherence
Availability: InStock
Author: belluga

Enforce Flutter architecture governance across presentation, domain, and infrastructure layers.

Updated Nov 7, 2025

Search Tags:#architecture #routing #presentation #state-management #flutter #controllers #guardrails

Ready to run

npx skills add https://github.com/belluga/delphi-ai --skill flutter-architecture-adherence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flutter-architecture-adherence
Source: https://github.com/belluga/delphi-ai/tree/main/.cline/skills/flutter-architecture-adherence
Command: npx skills add https://github.com/belluga/delphi-ai --skill flutter-architecture-adherence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flutter architecture adherence provides a centralized guardrail to prevent architectural erosion when making Flutter changes across presentation, domain, and data layers. It ensures proper separation of concerns, consistent use of sub-skills, and enforcement of setState usage and controller patterns.

Core Features & Use Cases

Serves as the umbrella entrypoint to coordinate required sub-skills (screen/workflow, controller, repository, route, and state heuristics) for architecture-impacting Flutter changes.
Enforces canonical sources, runnable lint contracts, and strict analyzer workflows to keep Flutter code aligned with governance documents and quality gates.
Reduces architectural drift by codifying rules, promoting testability, and enabling deterministic delivery across Flutter modules.

Quick Start

Review the Flutter architecture guardrails and apply the recommended sub-skills before changing any presentation, domain, or infrastructure code.

Frequently Asked Questions about flutter-architecture-adherence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent Flutter architecture drift when modifying UI and domain layers?▼

To prevent Flutter architecture drift, you need architecture guardrails that enforce feature boundaries, route contracts, and proper state management across presentation, domain, and infrastructure layers. This ensures changes respect separation of concerns and canonical sources.

What is the best way to enforce state management and controller patterns in Flutter?▼

Enforcing state management and controller patterns in Flutter requires applying architecture guardrails that codify setState usage heuristics and coordinate sub-skills for controllers. This approach keeps code aligned with governance documents and promotes testability.

How do I run Dart analyzer checks to validate Flutter architecture governance?▼

To validate Flutter architecture governance, run the official command `fvm dart analyze --format machine` to apply analyzer contracts. This executes explicit gate checks against canonical sources to ensure code adheres to quality gates.

Does this Flutter architecture tool coordinate checks for routes and repositories?▼

Yes, this Flutter architecture tool serves as an umbrella entrypoint that coordinates required sub-skills for screens, controllers, repositories, routes, and widget state heuristics. It enforces end-to-end governance across all impacted layers.

When do I need to apply Flutter architecture guardrails during development?▼

You need to apply Flutter architecture guardrails before changing any presentation, domain, or infrastructure code. Reviewing the guardrails and applying recommended sub-skills beforehand prevents architectural erosion and ensures deterministic delivery.

Why does my Flutter code lose separation of concerns across feature boundaries?▼

Flutter code loses separation of concerns when UI changes bypass feature boundaries and route contracts. Without centralized architecture governance enforcing canonical sources and explicit gate checks, architectural drift occurs across presentation and domain layers.