skills.rest
auravibes-apps
auravibes-appsOFFICIAL
Explore all skills by this author →
GitHub

flutter-notifier-pattern

Migrate Riverpod controllers to notifiers and enforce notifier-use case boundaries in Flutter apps.

Updated Aug 23, 2026
Search Tags:#patterns#state-management#flutter#riverpod#migration-guide#code-architecture#notifier-pattern
One-click install
npx skills add https://github.com/auravibes-apps/auravibes --skill flutter-notifier-pattern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flutter-notifier-pattern
Source: https://github.com/auravibes-apps/auravibes/tree/main/.agents/skills/flutter-notifier-pattern
Command: npx skills add https://github.com/auravibes-apps/auravibes --skill flutter-notifier-pattern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when migrating Riverpod class-based providers from legacy controller naming to notifier naming and enforcing notifier vs usecase boundaries.

Core Features & Use Cases

  • Notifier-driven state: place mutable UI state in notifiers under a notifiers/ folder with explicit state transitions.
  • Clear boundaries: separate business logic into use cases and keep providers lightweight.
  • Migration guidance: follow file-layout conventions and a step-by-step migration checklist to move from *Controller to *Notifier.
  • Runtime adapter pattern: use runtime adapters to connect notifiers with use cases without creating tight coupling.

Quick Start

Rename controllers to notifiers, relocate them to notifiers/ with updated providers, and wire in a runtime adapter to connect use cases.

Frequently Asked Questions about flutter-notifier-pattern

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

FAQPage Schema
How do I migrate Riverpod controllers to notifiers in Flutter?▼

To migrate Riverpod controllers to notifiers, rename your classes, relocate them to a notifiers/ folder, update the providers, and wire in a runtime adapter to connect use cases safely.

What is the notifier pattern in Riverpod state management?▼

The notifier pattern in Riverpod places mutable UI state in notifiers under a notifiers/ folder with explicit state transitions, keeping providers lightweight and separating business logic into use cases.

How do I separate notifier and usecase boundaries in Flutter apps?▼

To separate notifier and usecase boundaries in Flutter, keep business logic in use cases and use a runtime adapter pattern to connect notifiers with use cases without creating tight coupling.

When should I use the Riverpod notifier pattern for state management?▼

You should use the Riverpod notifier pattern when migrating legacy controller naming to notifier naming and enforcing safe, testable state transitions across features in Flutter apps.

What file layout conventions are recommended for Flutter notifier patterns?▼

The recommended file layout for Flutter notifier patterns involves placing notifiers in a dedicated notifiers/ folder with updated providers, following a step-by-step migration checklist to ensure safe state transitions.

Does the Riverpod notifier pattern require tight coupling between notifiers and use cases?▼

No, the Riverpod notifier pattern uses a runtime adapter to connect notifiers with use cases, ensuring safe and testable state transitions without creating tight coupling between components.

Related Skills

Explore More Software Engineering Skills→
dangdungvndangdungvn

riverpod-providers

Explain Riverpod provider declaration and usage for Flutter state management.

Community
Intermediate
RIMTHAN-LABRIMTHAN-LAB
1

riverpod-state-management

Implement Riverpod state management in Flutter with providers and code generation.

Official
Advanced
code-sinobicode-sinobi

flutter-confidence-checks

Validate Flutter provider logic, repository mocks, and state transitions.

Community
Intermediate
TMHSDigitalTMHSDigital
2

mobile-flutter-state-management

Implement Riverpod, Bloc, or Provider state management in Flutter apps.

Community
Intermediate