CtrlK
BlogDocsLog inGet started
Tessl Logo

android-di

Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when setting up Hilt DI, component scoping, or defining modules. (triggers: **/*Module.kt, **/*Component.kt, @HiltAndroidApp, @Inject, @Provides, @Binds)

89

Quality

86%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Android Dependency Injection (Hilt)

Priority: P0

1. Bootstrap Hilt

  • Annotate Application class with @HiltAndroidApp.
  • Annotate Activities/Fragments with @AndroidEntryPoint.

See module templates for bootstrap and module examples.

2. Define Modules

  • Use @Binds (abstract class) over @Provides when possible — generates smaller code.
  • explicit with @InstallIn (SingletonComponent, ViewModelComponent).

See module templates for @Binds examples.

3. Prefer Constructor Injection

  • Use @Inject constructor(...) over field injection.
  • Use @AssistedInject for runtime parameters.

Anti-Patterns

  • No Manual Dagger Components: Use Hilt — it generates all wiring.
  • No Field Injection in Logic: Use constructor injection; field injection only in Android framework classes.

References

Repository
HoangNguyen0403/agent-skills-standard
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.