Using Storyteller Kotlin SDK Docs with AI Assistants#
AI coding assistants (ChatGPT, Claude, Copilot, etc.) work best when you provide both:
- Your app code (Gradle config, initialization code, and the UI integration point).
- Storyteller Kotlin SDK documentation context.
This page describes the recommended workflow.
Download llms.txt (AI Context)#
llms.txt aggregates the public docs into a single plain-text file that is easy to paste or attach to AI tools. Images are removed; headings and code examples are preserved.
Recommended Workflow#
- Share
llms.txtwith the AI assistant (attach or paste). - Share the relevant app files/snippets:
- Gradle setup (
settings.gradle(.kts), appbuild.gradle(.kts)) - SDK initialization (
Storyteller.initialize(...)) - The integration surface (Compose screen / Activity / Fragment)
- Ask for a concrete output: a patch-style diff, a minimal snippet, or a step-by-step checklist.
Rules for AI-Generated Code (Integration Safety)#
- Use only Storyteller public APIs that exist in the SDK and/or are documented in these pages.
- Do not invent optional parameters, config flags, or DTO fields unless the prompt requires them.
- Do not include secrets or PII in examples; use placeholders (e.g.,
[APIKEY],"user-id"). - Prefer Jetpack Compose components unless legacy XML Views are explicitly required.
- When referencing behavior or configuration, prefer the canonical docs URLs:
https://docs.getstoryteller.com/android/<PageName>/
Good Prompt Examples#
- "Here is my
Applicationand appbuild.gradle.kts. Add Storyteller initialization and aStorytellerStoriesRowto my Compose screen." - "I need to handle Storyteller deep links in
MainActivity. Here is my intent handling code; update it safely." - "We want to disable personalization for some users. Show how to configure tracking options during initialization."