agentleFS
Sign inStart free
krutikJainkrutikJain/android-agent-skills/.github/skills/android-di-hilt/SKILL.md

android-di-hilt

Skill14 starsChanged 8 months agoMITView on GitHub

Wire Android dependency injection with Hilt, scopes, testing overrides, and module ownership boundaries.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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: android hilt setup, inject viewmodel repository hilt, scope dependency in android.

    line 17
  2. Distinctive:

    Verify replacement strategy for tests with Hilt test modules, uninstall modules, or fakes at the right component boundary.

    line 28
  3. Distinctive:

    Prefer constructor injection for app code you own.

    line 32
  4. Distinctive:

    Use qualifiers and scope annotations deliberately.

    line 33
  5. Distinctive:

    Keep Hilt modules close to the ownership boundary they configure.

    line 34
  6. Distinctive:

    Treat test replacement as part of the design, not an afterthought.

    line 35
  7. Distinctive:

    Test overrides or fakes are planned at the right graph boundary.

    line 65

≈ “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 DI Hilt

When To Use

  • Use this skill when the request is about: android hilt setup, inject viewmodel repository hilt, scope dependency in android.
  • Primary outcome: Wire Android dependency injection with Hilt, scopes, testing overrides, and module ownership boundaries.
  • Reach for this skill when the hard part is component ownership, bindings, scopes, entry points, or test replacement. If the request is only about networking APIs or reducer design, use the neighboring skill instead.
  • Handoff skills when the scope expands:
  • android-testing-unit
  • android-networking-retrofit-okhttp

Workflow

  1. Identify the injection boundary first: app-wide singleton, activity-retained, ViewModel, worker, service, or entry point from unsupported framework code.
  2. Decide what should be bound: constructor injection, @Binds, @Provides, qualifiers, multibindings, or assisted injection.
  3. Match lifetime to scope explicitly so dependencies do not outlive their owner or rebuild too often.
  4. Verify replacement strategy for tests with Hilt test modules, uninstall modules, or fakes at the right component boundary.
  5. Hand off API-specific or architectural questions only after the DI graph ownership is correct.

Guardrails

  • Prefer constructor injection for app code you own.
  • Use qualifiers and scope annotations deliberately; ambiguous bindings are a graph smell, not a convenience.
  • Keep Hilt modules close to the ownership boundary they configure.
  • Treat test replacement as part of the design, not an afterthought.

Anti-Patterns

  • Making everything @Singleton to silence scope questions.
  • Hiding business construction logic inside giant @Provides methods when constructor injection would suffice.
  • Using Hilt modules as a dumping ground for unrelated bindings across modules.
  • Confusing DI graph ownership with app architecture ownership.

Review Focus

  • Component and scope alignment.
  • Binding style and qualifier clarity.
  • Unsupported-entry-point bridges and test replacement strategy.
  • Module ownership boundaries across features and core code.

Examples

Happy path

  • Scenario: Inject OrbitTasks repositories and dispatchers with clear Hilt scopes.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest

Edge case

  • Scenario: Swap fake dependencies in the XML fixture for deterministic tests.
  • Command: cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest

Failure recovery

  • Scenario: Catch DI-specific prompts before they drift into architecture-clean or networking.
  • Command: python3 scripts/eval_triggers.py --skill android-di-hilt

Done Checklist

  • Component lifetime matches dependency lifetime.
  • Binding style is explicit and testable.
  • Test overrides or fakes are planned at the right graph boundary.
  • Non-DI work is handed off instead of buried in modules.

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