SkillsAdd

krutikjain/android-agent-skills

android-di-hilt

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

First seen Mar 7, 2026

Installation

$ npx skills add krutikjain/android-agent-skills --skill android-di-hilt
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-aigateway Shared topics
microsoft/azure-skills

Configure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: sem…

566.3K installs
azure-compute Shared topics
microsoft/azure-skills

Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compar…

510K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
prisma-cli Shared topics
prisma/skills

Prisma ORM CLI commands reference covering init, generate, migrate, db, dev, complete, studio, …

267K installs
supabase Shared topics
supabase/agent-skills

Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge F…

263K installs

Also in this package

Other skills from krutikjain/android-agent-skills · top by installs.

npx skills add krutikjain/android-agent-skills
android-kotlin-core 304 android-gradle-build-logic 303 android-testing-unit 294 android-compose-foundations 292 android-architecture-clean 289 android-coroutines-flow 257 android-networking-retrofit-okhttp 254 android-material3-design-system 147 android-room-database 121 android-mobile-frontend-design 63

Browse all from krutikjain/android-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 14
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
More 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"]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,532 B
  • docs SUMMARY.md 124 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 335 installs

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