Android Di logo

Android Di

Community
HoangNguyen0403
android-di

Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when changing the production Hilt graph; defer test overrides, Room wiring, navigation-specific scopes, and generic DI explanations to their specific skills.

Overview

PublisherHoangNguyen0403
Repositoryagent-skills-standard
Skill nameandroid-di
Stars
569
Forks
164
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by HoangNguyen0403 on GitHub. Read the source before you install it.

Installation

Install the Android Di AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git /tmp/agent-skills-standard
mkdir -p .claude/skills
cp -r /tmp/agent-skills-standard/skills/android/android-di .claude/skills/android-di
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Android Di in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Android Di on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Android Di is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Android Dependency Injection (Hilt)

Priority: P0 (CRITICAL)

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Android Di AI skill do?

Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when changing the production Hilt graph; defer test overrides, Room wiring, navigation-specific scopes, and generic DI explanations to their specific skills.

Why use Android Di on TypingMind?

Because you install it once and use it with any model. Android Di is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Android Di in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/HoangNguyen0403/agent-skills-standard/tree/develop/skills/android/android-di. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Android Di?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Android Di?

As many as you like. As long as a model supports skills, you can use Android Di with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Android Di AI skill free?

Yes. It is published on GitHub by HoangNguyen0403 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇