flutter-architect

Translate product requirements into Flutter feature scaffolds with Riverpod and go_router.

Updated Mar 27, 2026

Search Tags:#architecture #scaffolding #flutter #riverpod #code-generation #go_router #repository-pattern

Ready to run

npx skills add https://github.com/adona9/flutter-dev-team-skills --skill flutter-architect-adona9

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flutter-architect
Source: https://github.com/adona9/flutter-dev-team-skills/tree/main/flutter-architect
Command: npx skills add https://github.com/adona9/flutter-dev-team-skills --skill flutter-architect-adona9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates product requirements into a concrete, file-ready Flutter feature structure and enforces architectural guardrails using Riverpod, Repository pattern, and go_router.

Core Features & Use Cases

Implements a clean architecture scaffold: domain, data, and presentation layers with proper separation.
Validates specs before scaffolding and produces complete, compilable repository structures.
Supports multi-feature projects with consistent naming and layer rules.

Quick Start

Describe the feature and run the scaffold to generate a complete feature skeleton.

Frequently Asked Questions about flutter-architect

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

FAQPage Schema

How do I scaffold a Flutter feature with Riverpod and go_router?▼

Scaffolding a Flutter feature with Riverpod and go_router involves translating product requirements into a complete feature skeleton across domain, data, and presentation layers. The process enforces layer boundaries, validation rules, and naming conventions to produce compilable repository structures.

What is clean architecture in Flutter for multi-feature projects?▼

Clean architecture in Flutter separates domain, data, and presentation layers to enforce boundaries and validation rules. For multi-feature projects, scaffolding generates entities, repositories, use cases, data sources, and presentation layers with consistent naming conventions across screens.

Does the Flutter scaffold support the Repository pattern and use cases?▼

Yes, the Flutter scaffold fully supports the Repository pattern and use cases by generating complete, compilable repository structures. It produces entities, repositories, use cases, and data sources across domain and data layers with enforced layer boundaries.

Can I generate presentation layers and multiple screens from a spec?▼

Yes, you can generate presentation layers and multiple screens directly from a product spec. The scaffold translates requirements into a complete feature structure, producing presentation layers across multiple screens while enforcing validation rules and naming conventions.

What is the best way to enforce naming conventions in Flutter code generation?▼

The best way to enforce naming conventions during Flutter code generation is to validate specs before scaffolding. This ensures complete, compilable artifacts with consistent layer rules, validation rules, and naming conventions defined by architectural guardrails across multi-feature projects.