krutikJain/android-local-persistence-datastore
skills/android-local-persistence-datastore/SKILL.md
Persist lightweight user and app preferences with DataStore, schema-safe models, and migration-aware defaults.
$ install --global
skillsauthnpx skillsauth add krutikJain/android-agent-skills android-local-persistence-datastoreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 12:35 PM159.4s6 files scanned
SKILL.md
- name:
- android-local-persistence-datastore
- description:
- Persist lightweight user and app preferences with DataStore, schema-safe models, and migration-aware defaults.
- version:
- 0.1.0
- category:
- data-platform
- tags:
- ["android", "datastore", "preferences", "local-storage"]
- include:
- ["android datastore setup", "replace sharedpreferences android", "typed local preferences android", "datastore migration", "persist user toggle android"]
- exclude:
- ["room relation only", "compose focus order", "agp compatibility only"]
- owners:
- ["@android-agent-skills/maintainers"]
- test_targets:
- ["examples/orbittasks-compose", "examples/orbittasks-xml", "benchmarks/triggers.jsonl"]
Android Local Persistence DataStore
When To Use
- Use this skill when the request is about: android datastore setup, replace sharedpreferences android, typed local preferences android.
- Primary outcome: Persist lightweight user and app preferences with DataStore, schema-safe models, and migration-aware defaults.
- Handoff skills when the scope expands:
android-room-databaseandroid-modernization-upgrade
Workflow
- Confirm the data source, persistence boundary, sync model, and device capability involved.
- Model contracts explicitly before wiring network, storage, media, or background APIs.
- Apply the recommended AndroidX or platform pattern with migration-safe defaults.
- Validate offline, retry, and process death behavior against the sample apps and scenarios.
- Escalate security, performance, or release risk to the linked supporting skills when needed.
Guardrails
- Prefer typed models and explicit serializers over ad-hoc maps or bundles.
- Keep background work idempotent and cancellation-aware.
- Do not leak storage, media, or networking details into presentation code.
- Treat user data durability, privacy, and migration paths as part of the implementation.
Anti-Patterns
- Blocking the main thread with disk or network calls.
- Treating retryable sync failures as terminal user-facing errors.
- Mixing cache models and wire models without a mapping layer.
- Requesting broad storage or notification capabilities when a narrower API exists.
Examples
Happy path
- Scenario: Store reminder and filter preferences for OrbitTasks safely.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest
Edge case
- Scenario: Migrate old preference keys without breaking the XML fixture.
- Command:
cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest
Failure recovery
- Scenario: Avoid mixing lightweight preference storage requests with Room persistence work.
- Command:
python3 scripts/eval_triggers.py --skill android-local-persistence-datastore
Done Checklist
- The implementation path is explicit, minimal, and tied to the right Android surface.
- Relevant example commands and benchmark prompts have been exercised or updated.
- Handoffs to adjacent skills are documented when the request crosses boundaries.
- Official references cover the chosen pattern and the main migration or troubleshooting path.
Official References
- https://developer.android.com/topic/libraries/architecture/datastore
- https://developer.android.com/codelabs/android-preferences-datastore
- https://developer.android.com/training/data-storage/shared-preferences
- https://developer.android.com/topic/libraries/architecture/datastore#proto-datastore
Related Skills
krutikJain/android-testing-ui
testing
VerifiedTrustedCommunity
Validate Android UI behavior with Compose UI tests, Espresso-style checks, screenshot assertions, and accessibility verification.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-state-management
data-ai
VerifiedTrustedCommunity
Model screen state, events, reducers, and side effects for Android UIs with predictable lifecycle-aware ownership.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-serialization-offline-sync
tools
VerifiedTrustedCommunity
Coordinate serialization, caching, conflict handling, and offline-first sync flows in Android apps.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-security-best-practices
development
VerifiedTrustedCommunity
Apply Android app security guidance around secrets, storage, network trust, exported components, and least privilege.
5SKILL.mdUpdated Apr 25, 2026