FL
flutter-riverpod-change
Guide Dart, Flutter, Riverpod, Forui, routing, model, serializer, and UI-state changes in Genesix. Use when touching lib/features, lib/shared, providers, widgets, routes, generated Dart annotations, or Flutter package APIs.
Install
mkdir -p .claude/skills/flutter-riverpod-change && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15955" && unzip -o skill.zip -d .claude/skills/flutter-riverpod-change && rm skill.zipInstalls to .claude/skills/flutter-riverpod-change
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Guide Dart, Flutter, Riverpod, Forui, routing, model, serializer, and UI-state changes in Genesix. Use when touching lib/features, lib/shared, providers, widgets, routes, generated Dart annotations, or Flutter package APIs.223 chars✓ has a “when” trigger
About this skill
Flutter Riverpod Change
Use this skill before changing Flutter application code.
Workflow
- Read relevant local files and neighboring patterns.
- Check
pubspec.yamlbefore using third-party package APIs. - Identify whether annotations require
dart run build_runner build -d. - Keep feature code under
lib/features/<feature>/...and shared code underlib/shared/.... - Reuse Riverpod and UI patterns already present in the feature.
- Keep widgets presentation-focused; move business decisions out of UI.
Rules
- Prefer
@riverpodgenerator patterns when they match the feature and installed version. - Do not introduce Hook-based or alternate state management unless already used or requested.
- Prefer Forui when it fits existing UI.
- Reuse shared widgets and utilities before creating new ones.
- Do not declare named nested functions; extract private methods, helpers, or widgets.
- Do not manually patch
*.g.dartor*.freezed.dart.
Validation
Run checks from AGENTS.md based on the changed surface. Use dart run build_runner build -d before dart analyze when generator annotations changed.