// Reference map for support-arch 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.
| name | support-arch-reference-map |
| description | Reference map for support-arch 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. |
| argument-hint | Describe the feature, type, or consumer workflow you are trying to place or understand |
request/, UI scaffolding goes to ui/, adapters and holders go to recycler/.support-arch-kdoc-dokka skill so the published docs stay aligned.Understand and change support-arch build logic, module dependencies, version catalog entries, Dokka setup, KSP wiring, and shared Gradle conventions. Use for buildSrc edits, new dependencies, module graph changes, or documentation pipeline work.
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.
Write or improve KDoc for public APIs in support-arch. Use for Dokka updates, class docs, function docs, property docs, consumer-facing documentation, and explaining how downstream apps should use or extend library APIs.