ManageProviderQuery

Define standardized Riverpod query providers for reactive data streams.

1|Updated Sep 22, 2025

Search Tags:#architecture #query #state-management #flutter #riverpod #providers

Ready to run

npx skills add https://github.com/pretodev/nice_app --skill manageproviderquery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ManageProviderQuery
Source: https://github.com/pretodev/nice_app/tree/main/.trae/skills/ManageProviderQuery
Command: npx skills add https://github.com/pretodev/nice_app --skill manageproviderquery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Query providers are essential for decoupling UI from data sources by exposing pre-configured, reactive data streams that UI components can consume without knowledge of repositories.

Core Features & Use Cases

Establishes clear conventions for file structure and naming (_query.dart), enabling predictable code organization.
Defines when to use query providers versus commands, supporting real-time streams and future-based fetches across features.
Guides integration with Riverpod repositories and feature directories to promote separation of concerns and testability.

Quick Start

Create a new Riverpod query provider for a given feature following these conventions.

Frequently Asked Questions about ManageProviderQuery

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

FAQPage Schema

How do I structure Riverpod query providers to separate UI from data sources?▼

Riverpod query providers decouple UI from data sources by exposing pre-configured, reactive data streams. They allow UI components to consume repository data directly without needing knowledge of the underlying data retrieval logic.

When should I use query providers versus command providers in Flutter state management?▼

Use query providers in Flutter state management for real-time streams and future-based data fetching. This distinguishes them from command providers, which handle distinct user actions or mutations rather than continuous data exposure.

What is the standard file naming convention for Riverpod query providers?▼

The standard naming convention for Riverpod query providers is using the _query.dart suffix. This establishes predictable code organization across feature modules, ensuring data fetching logic is easily identifiable.

How do I access repository data within Riverpod query providers?▼

Access repository data within Riverpod query providers by applying standardized repository access patterns. This enforces a clear separation of concerns and ensures minimal business logic within the queries to maintain testability.

Can I include business logic inside Flutter query providers?▼

You should not include business logic inside Flutter query providers. They impose minimal business logic constraints to ensure testability and reliability, focusing purely on exposing reactive data streams to the UI.

Does ManageProviderQuery support real-time data streams in Flutter feature modules?▼

ManageProviderQuery supports real-time streams and future-based data fetching across Flutter feature modules. It applies standardized conventions to ensure predictable code organization and reliable data exposure.