agentleFS
Sign inStart free
krutikJainkrutikJain/android-agent-skills/.github/skills/android-room-database/SKILL.md

android-room-database

Skill14 starsChanged 8 months agoMITView on GitHub

Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the request is about: room database android, dao query migration android, room schema export.

    line 17
  2. Distinctive:

    Start with the persistence contract: entities, keys, indexes, relations, and whether the data is source-of-truth, cache, or offline-first …

    line 25
  3. Distinctive:

    Keep entities persistence-focused.

    line 33
  4. Distinctive:

    Use explicit transactions for multi-step writes that must remain consistent.

    line 34
  5. Distinctive:

    Test migrations against real old schemas before trusting them in release builds.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Android Room Database

When To Use

  • Use this skill when the request is about: room database android, dao query migration android, room schema export.
  • Primary outcome: Model Room entities, DAOs, transactions, migrations, schema exports, and test-safe local persistence.
  • Reach for this skill when the hard part is schema design, DAO queries, transactions, migrations, or Room testing. Hand off to android-rxjava-to-coroutines-migration only if the main work is reactive API migration rather than the database contract itself.
  • Handoff skills when the scope expands:
  • android-local-persistence-datastore
  • android-testing-unit

Workflow

  1. Start with the persistence contract: entities, keys, indexes, relations, and whether the data is source-of-truth, cache, or offline-first state.
  2. Model DAO access patterns explicitly, including transaction boundaries, query shape, paging, and invalidation behavior.
  3. Plan schema evolution before changing entities: exported schemas, migration steps, auto-migration eligibility, and destructive-fallback policy.
  4. Validate migration and query behavior with deterministic tests rather than assuming Room annotations are enough.
  5. Hand off DataStore, sync, or reactive API questions only after the Room boundary is correct.

Guardrails

  • Export schemas and treat them as part of the contract, not optional tooling noise.
  • Keep entities persistence-focused; map to domain/UI models instead of leaking table shape upward.
  • Use explicit transactions for multi-step writes that must remain consistent.
  • Test migrations against real old schemas before trusting them in release builds.

Anti-Patterns

  • Treating Room entities as the app's domain model everywhere.
  • Editing schemas without exporting or validating migration paths.
  • Writing broad SELECT * queries when the screen only needs a narrow projection.
  • Collapsing database, sync, and reactive-stream migration problems into one undifferentiated task.

Review Focus

  • Entity keys, indexes, relations, and schema ownership.
  • DAO query shape, transactions, and invalidation behavior.
  • Migration safety, schema exports, and test coverage.
  • Clear boundaries between Room models and higher-level app models.

Examples

Happy path

  • Scenario: Persist task items and reminder flags with schema-aware entities.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest

Edge case

  • Scenario: Recover from a failed schema change with an explicit migration path.
  • Command: python3 scripts/eval_triggers.py --skill android-room-database

Failure recovery

  • Scenario: Keep Room requests separate from DataStore, networking, and modernization prompts.
  • Command: cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest

Done Checklist

  • Entities, DAOs, and transactions match the real persistence contract.
  • Schema export and migration strategy are explicit.
  • Query and migration tests cover the risky paths.
  • Non-Room concerns are handed off instead of mixed into the database task.

Official References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free