agentleFS
kaeawckaeawc/auto-mobile/android/CLAUDE.md

auto-mobile / android

CLAUDE.md56 starsChanged 34 days agoApache-2.0View on GitHub

Quick reference for AI agents working in android/. Run all commands from the repo root unless noted.

The file

We split this CLAUDE.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer ./gradlew -p android to avoid changing directories.

    line 16
  2. Very specific:

    Every other module (control-proxy, auto-mobile-sdk, video-server, junit-runner, protocol, playground/*, ...) uses manual constructor …

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

AutoMobile Android

Quick reference for AI agents working in android/. Run all commands from the repo root unless noted.

Project Layout

  • android/ - Android Kotlin Gradle project (apps, libraries, JUnit runner)
  • android/ide-plugin/ - IntelliJ/Android Studio plugin (Gradle project)

Common Commands (from repo root)

  • ./gradlew -p android <task>
  • ./gradlew -p android :junit-runner:test
  • ./gradlew -p android :control-proxy:assembleDebug
  • ./gradlew -p android :ide-plugin:build

Notes

  • Prefer ./gradlew -p android to avoid changing directories.
  • Android validation scripts live under scripts/ktfmt/, scripts/xml/, and scripts/android/.
  • Kotlin is formatted with ktfmt --google-style (2-space block + 2-space continuation indent), pinned in scripts/ktfmt/install_ktfmt.sh. Auto-format touched files with scripts/ktfmt/apply_ktfmt.sh; CI enforces it tree-wide via scripts/ktfmt/validate_ktfmt.sh.

Dependency Injection

  • Metro is the only DI framework allowed in android/; Koin, Dagger and Hilt are not used and must not be introduced. Metro is opt-in per module and applied in that module's own build file (the root declares the plugin with apply false). Today only desktop-app (graph root) and desktop-core (contributions) use it.
  • Every other module (control-proxy, auto-mobile-sdk, video-server, junit-runner, protocol, playground/*, ...) uses manual constructor injection with interfaces and fakes; ide-plugin resolves IntelliJ platform services through the platform API. The SDK's Kotlin object facades are a deliberate zero-setup public API, not a missing graph.
  • A new module starts with constructor injection and adds Metro only when it owns a root @DependencyGraph. Per-module evidence and the control-proxy lateinit note are in docs/design-docs/plat/android/dependency-injection.md.

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.

Reviews can't be read right now.

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.