使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/thiennc-tesoglobal/flutter-skills --skill flutter-persistence開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Flutter Persistence
Choose storage from data shape, query needs, durability, sensitivity, synchronization, and migration requirements.
Select proportionately
- Use preferences only for small settings, not relational or critical domain data.
- Use files for document/blob ownership with explicit atomicity and cleanup.
- Use a database when queries, relationships, transactions, indexing, or migration justify it.
- Use platform secure storage for small secrets; do not treat ordinary app databases as secret vaults.
- Preserve an established package unless it cannot satisfy a concrete requirement.
Model ownership
Define the source of truth, cache freshness, write ordering, conflict behavior, offline mutations, deletion semantics, and recovery from corrupt or incompatible data. Keep storage models behind repositories so schema details do not leak into widgets.
Load references conditionally
- Read caching policy when choosing cache keys, freshness, invalidation, eviction, stale disclosure, or user isolation.
- Read offline synchronization when local and remote data can diverge, mutations queue offline, background work runs, or conflicts and deletions must reconcile.
Route HTTP validators and transport caching to flutter-networking, and image, widget, scroll, or memory-cache performance to flutter-performance.
Migration and safety
Version schemas and test upgrades from realistic prior versions. Never destroy user data as an automatic response to a migration failure unless the product explicitly permits it. Avoid storing access tokens, passwords, or sensitive personal data in logs or plain preferences.
Verification
Test first run, reopen, upgrade, failed write, concurrent access, corrupted data, deletion, and offline/online transitions relevant to the feature. Use temporary databases or directories for deterministic tests.
