Composables

Android Local Persistence Datastore

Community

krutikJain

Persist lightweight user and app preferences with DataStore, schema-safe models, and migration-aware defaults.

Overview

Repository
krutikJain/android-agent-skills
Publisher
krutikJain
Stars
14
Forks
5
Bundled files
5
License
MIT
Updated
Mar 25, 2026

Installation

tmp=$(mktemp -d)
git clone --depth 1 https://github.com/krutikJain/android-agent-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/android-local-persistence-datastore" ~/.claude/skills/android-local-persistence-datastore
rm -rf "$tmp"

Instructions

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-database
  • android-modernization-upgrade

Workflow

  1. Confirm the data source, persistence boundary, sync model, and device capability involved.
  2. Model contracts explicitly before wiring network, storage, media, or background APIs.
  3. Apply the recommended AndroidX or platform pattern with migration-safe defaults.
  4. Validate offline, retry, and process death behavior against the sample apps and scenarios.
  5. 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

Bundled files

FAQ

What does Android Local Persistence Datastore do?

Persist lightweight user and app preferences with DataStore, schema-safe models, and migration-aware defaults.

Who made Android Local Persistence Datastore?

krutikJain (a community member) publishes it in the krutikJain/android-agent-skills repository on GitHub.

Is Android Local Persistence Datastore free?

Yes. Android Local Persistence Datastore is open source, published by krutikJain under the MIT license.

What comes with Android Local Persistence Datastore?

Its instructions and 5 files the agent reads only when a task needs them, such as references, examples or scripts.

Which agents can use Android Local Persistence Datastore?

Any coding agent that reads SKILL.md files, including Claude Code, Codex, Cursor, GitHub Copilot and Gemini CLI. The agent loads the skill when a task matches its description.

What are agent skills?

An agent skill is a folder with a SKILL.md file: instructions that teach a coding agent how to do one kind of task, and optionally files it can read while it works. The agent keeps only the skill's name and description in mind and reads the rest when a task calls for it.

How are agent skills different from MCP servers?

An MCP server gives an agent new tools to call, code that runs somewhere and returns results. A skill gives it knowledge: how to approach a task with the tools it already has. Many agents use both.

How can my agent test my Android app?

Robomori lets coding agents create, start and control Android emulators and devices from one command, so they can install your app, take screenshots and check dark mode, font sizes and languages.

You're subscribed

The next lesson lands in on Wednesday.