Skip to content
Grona Developers

Use these docs with AI tools

This site publishes its content as plain text for large language models, following the llms.txt convention. Give one of these files to Claude, Cursor or another coding assistant, and it can answer questions and write integration code from the current Grona docs instead of from what it remembers.

The files

Section titled “The files”
File What it contains Use it when
/llms.txt A short index: what Grona is and links to the two files below A tool discovers documentation on its own and looks for llms.txt
/llms-full.txt The complete documentation as one Markdown file Your tool has room for the whole site and you want every detail
/llms-small.txt An abridged version, with notes, tips and extra whitespace removed The full file is too large for your tool’s context, or you want faster answers

The files are generated from the same source as these pages every time the site is published, so they are never behind the pages.

Point your tool at the docs

Section titled “Point your tool at the docs”
  • Claude. In Claude Code, ask Claude to fetch https://developer.grona.ai/llms-full.txt before it works on your Grona integration, or save the file in your repository and reference it. In the Claude apps, download the file and attach it to the conversation or the project.
  • Cursor. Add https://developer.grona.ai/llms-full.txt as a documentation source and reference it in chat, or save the file in your repository and reference the file.
  • Other assistants. Give the tool the URL of llms-full.txt if it can fetch web pages. Otherwise, download the file, or llms-small.txt if the full file does not fit, and add it to the tool’s context.

A prompt that names the surface and the page gets better results, for example: “Using the Grona docs in llms-full.txt, write the Application class that initialises the Grona Android SDK for workspace key acme-market.”

What is not available

Section titled “What is not available”

Grona does not provide an MCP server. Check generated code against the page it came from, especially exact method names, option names and endpoint paths, before you ship it.

Next steps

Section titled “Next steps”