Flutter Riverpod Clean Architecture Skill
Flutter clean arch w/ Riverpod 3.x codegen, Freezed 3.x sealed, GoRouter, Hive CE persist.
Disclaimer: Unofficial. No affiliation w/ Google, Flutter team, Riverpod maintainers. "Flutter" trademark Google LLC. "Riverpod" by Remi Rousselet.
Highly opinionated by design: This skill intentionally favors a strict
Riverpod/codegen/clean-architecture workflow over broad Flutter flexibility.
Treat it as a project policy package, not a neutral best-practices checklist.
Until v1.0.0, assume every release may include breaking changes as the policy
surface is refined.
Installation
Install this as a plugin, not as a raw skill, when you want enforcement. Raw
Agent Skills installs only provide prompt guidance; they cannot register hooks
or run scanners.
Claude Code
/plugin marketplace add sgaabdu4/building-flutter-apps
/plugin install building-flutter-apps@building-flutter-apps
Reads .claude-plugin/marketplace.json + .claude-plugin/plugin.json.
Auto-loads hooks/hooks.json:
- PostToolUse (
dart_gate.sh) — grep + awk checks after every Write|Edit|MultiEdit; blocks turn with violation reason.
- Stop (
preflight_audit.sh) — full repo audit + dart analyze --fatal-infos before turn ends.
- UserPromptSubmit (
skill_reminder.sh) — top-5 rules reminder per turn in Flutter projects.
Codex CLI
codex features enable hooks
codex features enable plugin_hooks
codex plugin marketplace add sgaabdu4/building-flutter-apps
codex
/plugins
In /plugins, choose the building-flutter-apps marketplace tab, open the
building-flutter-apps plugin, and select Install plugin.
Reads .codex-plugin/plugin.json from the installed plugin. Codex marketplaces
can be added from GitHub shorthand (owner/repo), Git URLs, SSH URLs, or local
marketplace roots; Codex also recognizes repo-local
.claude-plugin/marketplace.json entries. Auto-loads the manifest-declared
hooks/hooks.json — same PostToolUse/Stop/UserPromptSubmit events, same
scripts as Claude.
The hooks feature enables Codex lifecycle hooks. Current Codex builds also
require plugin_hooks for plugin-bundled lifecycle configs. If you edit
~/.codex/config.toml directly, use:
[features]
hooks = true
plugin_hooks = true
Public Codex docs may still show codex_hooks for the lifecycle hook gate.
Use the CLI commands above on current Codex builds; codex features list
shows the feature key your installed CLI accepts.
Copilot CLI
copilot plugin marketplace add sgaabdu4/building-flutter-apps
copilot plugin install building-flutter-apps@building-flutter-apps
Reads .github/plugin/marketplace.json + root plugin.json. Auto-loads hooks/hooks.copilot.json (camelCase event names, bash/powershell fields per Copilot schema):
- postToolUse →
dart_gate.sh
- agentStop →
preflight_audit.sh
- userPromptSubmitted →
skill_reminder.sh
All scripts no-op outside Flutter projects (gated on upward pubspec.yaml discovery).
Enforcement model
Install-time script execution is not a safe assumption across agent runtimes.
The enforceable contract is:
- Plugin install wires hooks for Claude Code, Codex CLI, and Copilot CLI.
- First Flutter prompt/edit/stop proves hooks are active because the
UserPromptSubmit, PostToolUse, and Stop/agentStop hooks fire from the
installed plugin.
- Project CI remains the hard gate through
dart analyze with
flutter_skill_lints and riverpod_lint in analysis_options.yaml.
If a user installs only SKILL.md or copies ~/.agents/skills/building-flutter-apps,
none of the scanners run. Treat that as guidance-only mode.
Project bootstrap (one-time per Flutter project)
cp <plugin-cache>/references/analysis_options.yaml ./analysis_options.yaml
dart pub get
dart analyze # confirms wiring
flutter_skill_lints is an external analyzer plugin. List it ONLY under plugins: in analysis_options.yaml (NEVER in pubspec.yaml). The bundled analysis_options.yaml already wires it.
How drift is prevented
The skill enforces rules across SKILL.md, the reference docs, and the bundled
analyzer config via a 3-tier mechanism:
