사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
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.
