android-di-hilt

name	android-di-hilt
description	Wire Android dependency injection with Hilt, scopes, testing overrides, and module ownership boundaries.
metadata	{"version":"0.1.0","category":"foundations","tags":["android","hilt","dependency-injection","testing"],"triggers":{"include":["android hilt setup","inject viewmodel repository hilt","scope dependency in android","replace manual service locator","hilt testing override","android-di-hilt skill","scope dependency in android hilt","hilt component scope mismatch","hilt entry point android"],"exclude":["retrofit serialization only","compose typography only","gradle wrapper upgrade","collect flow in compose screen","state matrix before release"]},"owners":["@android-agent-skills/maintainers"],"test_targets":["examples/orbittasks-compose","examples/orbittasks-xml","benchmarks/triggers.jsonl"]}

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.