// Use when mapping SQLite query behavior, Room raw query integration, annotation processing flow, or current KSP code-generation behavior in support-query-builder.
| name | support-query-builder-sqlite-android-map |
| description | Use when mapping SQLite query behavior, Room raw query integration, annotation processing flow, or current KSP code-generation behavior in support-query-builder. |
| argument-hint | Describe the SQLite, Room, processor, or KSP question you need to answer. |
This skill provides a fast, source-backed map for how SQL is built, translated into Android SQLite query objects, and connected to Room via raw queries. It also maps current KSP behavior and KotlinPoet code-generation ownership.
Core principle: answer from module ownership and concrete file paths first, then use external docs to validate edge behavior.
@EntitySchema to generated schema object output.:core, :core:ext, :annotations, or :processor.Do not use this skill for general Gradle dependency editing. Use support-query-builder-build-dependencies for that.
| Question | Primary module | First file |
|---|---|---|
| Where does SQL string building happen? | :core | core/src/main/kotlin/co/anitrend/support/query/builder/core/QueryBuilder.kt |
Where does SupportSQLiteQuery come from? | :core:ext | core/ext/src/main/kotlin/co/anitrend/support/query/builder/core/ext/QueryBuilderExtension.kt |
Where is @EntitySchema defined? | :annotations | annotations/src/main/kotlin/co/anitrend/support/query/builder/annotation/EntitySchema.kt |
| Where is annotation processing entrypoint? | :processor | processor/src/main/kotlin/co/anitrend/support/query/builder/processor/Provider.kt |
| Where is KotlinPoet emission committed? | :processor | processor/src/main/kotlin/co/anitrend/support/query/builder/processor/factory/ClassFactory.kt |
| Where is KSP wired into sample usage? | :sample | sample/build.gradle.kts |
| How do I verify Android SQLite runtime capability? | :sample runtime diagnostics | SELECT sqlite_version(); and PRAGMA compile_options; |
import co.anitrend.support.query.builder.core.QueryBuilder
import co.anitrend.support.query.builder.core.ext.asSupportSQLiteQuery
import co.anitrend.support.query.builder.dsl.from
import co.anitrend.support.query.builder.dsl.select
val builder = QueryBuilder()
builder select "*" from "person"
// Bridge from pure query builder to Android Room raw-query input type
val sqliteQuery = builder.asSupportSQLiteQuery()
SupportSQLiteQuery is created in :core instead of :core:ext.Provider, Processor, and ClassFactory.from.extentions).| Excuse | Reality |
|---|---|
| "KSP folders exist, so migration is done" | Folder artifacts are not build wiring truth. Confirm plugin and processor APIs in source/build files. |
| "I can infer output path without reading processor code" | Verify the current KSP CodeGenerator and test-harness APIs instead of relying on outdated annotation-processing assumptions. |
| "Bridge code is obvious" | Verify owner module. This repo keeps SQL building and Android bridge in different modules. |
If any red flag appears, stop and reopen the reference maps.
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.
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.
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.
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.