13.1 — Android / Kotlin
An enterprise Android project means fifty Gradle modules, three build variants, environment flavors, and strict Clean Architecture. Claude Code absorbs this complexity provided your CLAUDE.md hands it the keys.
Start by documenting the exact Gradle commands: ./gradlew assembleGoogleInHouseRelease, ./gradlew :features:home:test, ./gradlew detekt. Without these commands, Claude Code can't validate its own work. Then, encode architectural rules as absolute constraints: a ViewModel never touches a Repository directly, it goes through a UseCase. Interfaces live in :domain:feature:external, implementations in :domain:feature:internal.
hooks are your permanent safety net. A PostToolUse hook that runs Detekt on modified files prevents style violations from reaching CI. A PreToolUse hook that checks imports respect architectural layers — no com.myapp.data.* in a ViewModel — acts as a real-time architectural linter.
Custom slash commands accelerate multi-module scaffolding. A /create-feature generates the UseCase, the Hilt module, the Repository interface and its implementation, and the ViewModel simultaneously, each in the right module. Figma MCP connects mockups to the workflow and enables generating Compose code that uses the project's design system components, not generic Material.
Key takeaways
On an enterprise Android project, the CLAUDE.md is your architectural contract. The more precise it is about inter-module dependencies and mandatory patterns, the more Claude Code produces code that passes CI on the first try.