flutter-riverpod-patterns
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-06-13
- Stars
- ★ 3
- Forks
- 1
03 SKILL.md 正文
Flutter Riverpod Patterns Skill
Production patterns for state management with Riverpod 2.x in Flutter.
Provider Types
1. Simple Provider (read-only data)
@riverpod
List<Novel> novels(Ref ref) {
return mockNovels;
}
2. AsyncNotifier Provider (async data with mutations)
@riverpod
class NovelsNotifier extends _$NovelsNotifier {
@override
Future<List<Novel>> build() async {
return _loadNovels();
}
Future<List<Novel>> _loadNovels() async {
// In production: API call
// For now: return mock data
return mockNovels;
}
Future<void> refresh() async {
state = const AsyncLoading();
state = AsyncData(await _loadNovels());
}
}
3. StateNotifier Provider (sync state with mutations)
@riverpod
class LibraryNotifier extends _$LibraryNotifier {
@override
LibraryState build() {
return LibraryState(
reading: [],
completed: [],
wishlist: [],
);
}
void addToReading(Novel novel) {
state = state.copyWith(
reading: [...state.reading, novel],
);
}
void moveToCompleted(String novelId) {
final novel = state.reading.firstWhere((n) => n.id == novelId);
state = state.copyWith(
reading: state.reading.where((n) => n.id != novelId).toList(),
completed: [...state.completed, novel],
);
}
}
4. Family Provider (parameterized)
@riverpod
Future<Novel> novelById(Ref ref, String id) async {
final novels = await ref.watch(novelsProvider.future);
return novels.firstWhere((n) => n.id == id);
}
Consuming Providers in Widgets
ConsumerWidget (stateless)
class HomeFeedScreen extends ConsumerWidget {
const HomeFeedScreen({super.key});
@override
Widget build(BuildContext context, WidgetRef ref) {
final novels = ref.watch(novelsProvider);
return novels.when(
data: (data) => ListView.builder(
itemCount: data.length,
itemBuilder: (context, index) => NovelCard(novel: data[index]),
),
loading: () => const Center(child: CircularProgressIndicator()),
error: (e, st) => Center(child: Text('Error: $e')),
);
}
}
ConsumerStatefulWidget (with local state)
class BrowseScreen extends ConsumerStatefulWidget {
const BrowseScreen({super.key});
@override
ConsumerState<BrowseScreen> createState() => _BrowseScreenState();
}
class _BrowseScreenState extends ConsumerState<BrowseScreen> {
String _selectedGenre = 'All';
@override
Widget build(BuildContext context) {
final novels = ref.watch(novelsProvider);
// ... filter by _selectedGenre
}
}
File Organization
lib/providers/
├── novels_provider.dart # Novel list + CRUD
├── library_provider.dart # User's library state
├── reader_settings_provider.dart # Reader preferences
├── audio_player_provider.dart # Audio playback state
└── providers.dart # Barrel export
Rules
- One provider file per domain entity
- Use
@riverpodannotation (code-gen) over manual providers - Run
dart run build_runner buildafter creating/modifying providers - Export all from
lib/providers/providers.dartbarrel file - Provider names follow pattern:
{entity}Provider,{entity}NotifierProvider
04 同仓库更多 Skills
hello-checker
Use this skill when asked to "verify", "check", or "validate" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.
ask-skill
暂无简介
html-review-artifact
Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML
converge-planning
Design a Converge playbook end-to-end. Use when the user says "plan a project", "design a playbook", "decompose into tasks", "scaffold a Converge workflow", "onboard to Converge", or asks how to write TASK.md / playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `/converge-control` after producing the playbook structure.
converge-control
Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says "run my playbook", "execute this", "monitor the run", "converge failed", "the run is stuck", "retry failures", "babysit this playbook", "what's the status?", "show me the gantt", or asks how to use `converge run` / `--select` / `inspect` / `doctor` / `clean` / `stop`. Also use it for `HTTP 401` / `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.
repair-taskts
Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors