// Understand and change android-emojify build logic, module dependencies, version catalog entries, Dokka setup, Spotless, and shared Gradle conventions. Use for buildSrc edits, new dependencies, module graph changes, or documentation pipeline work.
Write or improve KDoc for public APIs in android-emojify. Use for Dokka updates, class docs, function docs, property docs, consumer-facing documentation, and explaining how downstream apps should initialize or extend emoji library APIs.
Reference map for android-emojify modules, package roots, dependency direction, consumer entry points, and Dokka navigation. Use for questions like which module should own this code, where a class should live, what consumers should import, or how the library is organized.
Align jenv with .java-version and run Gradle reliably on low-RAM machines. Use for Java mismatch errors, Gradle OOMs, daemon memory pressure, and selecting safe build flags.
| name | android-emojify-build-dependencies |
| description | Understand and change android-emojify build logic, module dependencies, version catalog entries, Dokka setup, Spotless, and shared Gradle conventions. Use for buildSrc edits, new dependencies, module graph changes, or documentation pipeline work. |
| argument-hint | Describe the dependency, Gradle change, or build pipeline task you need to make |
buildSrc.io.wax911.emojify plugin wires modules together.gradle/libs.versions.toml first.buildSrc instead of duplicating it in several module build files.:contract) do not depend on higher layers (:emojify).buildSrc.:app is excluded from CI (settings.gradle.kts checks for the CI environment variable); do not rely on :app being present in automated builds.emojify:preTest → emojify:test → emojify:postTest in that order; always chain them.jenv-gradle-low-ram skill if Java selection or memory pressure becomes an issue.