AI coding assistants can integrate Storyteller faster when they work from the
real documentation instead of memory. The Storyteller SDK docs are published as
plain-text files that assistants can read. This section shows you how to give
an assistant those files, set up a project rule, and use the integration skill.
Tell your assistant your platform and SDK version. The docs describe the
current SDK releases. Give it your SDK's release notes when working with an
older version; your SDK's AI guide links to them.
Give it the values it needs for your app, such as category IDs. Keep API
keys in your app's existing configuration, and tell your assistant where the
app reads that configuration. Share only non-secret context.
{"slug": "ai-index", "page_title": "Build with AI", "page_url": "ai/", "canonical_url": "/ai/", "markdown": "# Build with AI\n\nAI coding assistants can integrate Storyteller faster when they work from the\nreal documentation instead of memory. The Storyteller SDK docs are published as\nplain-text files that assistants can read. This section shows you how to give\nan assistant those files, set up a project rule, and use the integration skill.\n\n## Start in three steps {#quick-start}\n\n1. **Give your assistant the docs for your platform.** Start with the\n [docs index](docs-for-ai.md#docs-index), or follow your\n [SDK's AI guide](docs-for-ai.md#sdk-guidance).\n1. **Add a project rule.** Tell your assistant which Storyteller SDK your app\n uses and where the docs are. See\n [Set up your coding assistant](coding-assistants.md).\n1. **Ask for one task at a time and check the result.** Compare the answer\n with the docs pages it came from, then build and test your app.\n\n## What's available {#available}\n\n| Tool | What it does | Where |\n| ---- | ------------ | ----- |\n| **Copy for AI** button | Copies a summary of the page plus the full page, ready to paste into a chat. **Copy as Markdown** copies only the page. | SDK topic pages |\n| Docs bundle | Gives your assistant the SDK documentation in one plain-text file. | `/<platform>/ai/llms.txt` |\n| Page files | The summary and full text of one page. | `/<platform>/ai/llms-<slug>.txt` |\n| Release notes and analytics files | Release notes and analytics events, which you can add when you need them. | `/<platform>/ai/llms-changelog.txt`, `/<platform>/ai/llms-analytics.txt` |\n| Docs index for AI | Lists every SDK bundle and API site, for assistants that read `llms.txt` files. | [`/llms.txt`](../llms.txt) |\n| Storyteller integration skill | Guides an assistant through an integration, audit, or troubleshooting session for your app. | [iOS and Android Showcase repositories](integration-skill.md) |\n\nFor platform-specific instructions and example prompts, use your\n[SDK's AI guide](docs-for-ai.md#sdk-guidance).\n\n## Give your assistant the right context {#limits}\n\n- **Tell your assistant your platform and SDK version.** The docs describe the\n current SDK releases. Give it your SDK's release notes when working with an\n older version; your [SDK's AI guide](docs-for-ai.md#sdk-guidance) links to them.\n- **Give it the values it needs for your app, such as category IDs.** Keep API\n keys in your app's existing configuration, and tell your assistant where the\n app reads that configuration. Share only non-secret context.\n\n## In this section {#in-this-section}\n\n- [Use the docs with AI](docs-for-ai.md): find the right SDK guidance and see\n which assistants can open docs links.\n- [Set up your coding assistant](coding-assistants.md): add a project rule\n that points your assistant at the docs for your platform.\n- [Use the Storyteller integration skill](integration-skill.md): a guided\n integration, audit, or troubleshooting session for iOS and Android apps.\n", "copy_markdown_include_header": false, "base_path": "", "ai_dir": "ai", "missing_payload_behavior": "empty"}