How to use the Flutter Riverpod State Management agent skill

What the riverpod skill makes the agent do

An agent skill is a folder with instructions that an AI assistant loads when a task matches the skill's description. This one covers Riverpod providers, consumers, refs, containers, overrides, async state, code generation, testing, and safe defaults.

Once installed, the agent chooses provider types using the skill's core rules, wires up ProviderScope at the app root, uses ref.watch in UI reads and ref.read for imperative reads, handles async data with AsyncValue, and writes provider tests with overrides. The skill is advice and patterns only. It does not run code, build projects or change files on its own; the agent still works through your normal tools and you review the output.

• Picks between Provider, StateProvider, FutureProvider, StreamProvider, Notifier and AsyncNotifier based on the job
• Keeps repositories and APIs outside widgets and business logic inside providers or notifiers
• Suggests autoDispose, family or keepAlive where they fit
• Writes tests through ProviderContainer and asserts AsyncValue states

Install the riverpod skill from a ZIP file

Download the ZIP for this skill from this page and unzip it. The skill is a single file named SKILL.md. Place the unzipped skill folder in one of two locations, depending on how you want to use it.

For all your projects, put it in your user skills folder at ~/.claude/skills/. To limit it to one project, put it in that project's .claude/skills/ folder instead. The project option is useful when a team wants everyone's assistant to follow the same Riverpod rules.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/ (the folder containing SKILL.md)
• Project install: the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload

Trigger the skill with natural requests

You do not need a special command. The skill is meant to load when your request is about Flutter Riverpod state management. Name Riverpod or a Riverpod concept in your request so the match is clear.

Be specific about the feature and the file or screen involved. The skill's guidance covers choosing a provider type, wiring the app, async loading, code generation and testing, so requests that touch those topics fit best.

• "Using Riverpod, add a provider that loads the user profile from our API with loading and error states."
• "Should this cart state be a Notifier or a StateProvider in our Riverpod setup?"
• "Write a provider test with ProviderContainer that overrides the repository."
• "Add ProviderScope to our app root and show how to read a provider from a ConsumerWidget."

Know what you need before you start

The skill assumes a working Flutter and Dart toolchain. Which packages you add depends on the code you write. Flutter UI code uses flutter_riverpod. Dart-only code uses riverpod. The skill notes that flutter_riverpod brings in riverpod, so you usually do not add both.

If you use code generation, you also need riverpod_annotation, riverpod_generator and build_runner. The skill recommends using matching versions from the same 3.x release line. Check the package versions your project already uses before adding these.

• Flutter and Dart toolchain
• flutter_riverpod (3.x line) for Flutter apps, or riverpod for Dart-only code
• riverpod_annotation, riverpod_generator and build_runner if code generation is used

Safety notes: scripts and network

This skill runs no scripts and uses no network access. It is a single SKILL.md file of instructions, so installing it does not add executable code to your machine.

The skill does not check your code for correctness. The output of the agent still needs a developer to review and run it, especially generated code and tests.

• Runs scripts: no
• Uses network: no
• Licence: MIT

Tips for getting better results from the skill

Give the agent your context. The skill asks for the smallest working provider first and notes about whether ProviderScope is required, whether a provider should be autoDispose or cached, and whether a family is needed. If you already have these decisions made, say so in the request.

If your app uses a different state library such as Bloc or Provider alone, this skill will not match your codebase. Tell the agent which library your project uses, or pick a different skill.

• Name the file or feature so the agent reads the right code
• Mention your Riverpod version if it is not the 3.x line
• Ask for test override notes whenever a provider depends on an external service