// Reference map for support-query-builder 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.
Use when mapping SQLite query behavior, Room raw query integration, annotation processing flow, or current KSP code-generation behavior in support-query-builder.
Understand and change support-query-builder 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 publishing pipeline work.
Write or improve KDoc for public APIs in support-query-builder. Use for Dokka updates, class docs, function docs, property docs, consumer-facing documentation, and explaining how downstream apps should use or extend library APIs.
| name | support-query-builder-reference-map |
| description | Reference map for support-query-builder 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 |
:core, Room integration goes to :core:ext, annotation definitions go to :annotations, code generation goes to :processor.support-query-builder-kdoc-dokka skill so the published docs stay aligned.support-query-builder-sqlite-android-map