Using AI Assistants

AI coding assistants such as Claude, GitHub Copilot or Cursor know FireMonkey well, but they have seen little Gorilla3D code. Without the documentation they tend to guess class names, properties and methods, or fall back to standard FMX components like TViewport3D, which are not compatible with Gorilla3D. This page shows how to give your assistant the complete, version-matching Gorilla3D documentation.

There are two ways:

Option Best for Content
Claude Skill Claude Code, Claude Desktop, claude.ai The complete documentation of one version as a ZIP, including rules and an index
llms.txt Any other AI tool or chatbot An index and a single-file version of the documentation, available online

Claude Skill

A skill is a folder with instructions and reference material that Claude loads automatically when a task matches. Claude first only sees the name and description of the skill. When you work on Gorilla3D code, it reads the skill's overview and then only the documentation pages it needs, for example the particle reference for a particle effect. This keeps the context free for your own code.

Download

Open the version overview of the documentation (click Version Overview or select a version on the start page) and click Export for AI. You receive a ZIP file named like gorilla3d-v1-5-skill-2026-10-13.zip.

Direct download for this version: https://docs.gorilla3d.de/export/zip?version=v1.5

Important: Use the skill of the Gorilla3D version you develop with. The API changes between versions, and the skill only describes the version it was exported from.

The ZIP contains one folder:

gorilla3d-v1-5/
├── SKILL.md       rules for Gorilla3D development and an overview of all sections
├── INDEX.md       every page with a short description
├── references/    all documentation pages as Markdown, same structure as this site
└── data/images/   images used by the pages

Install in Claude Code

Unzip the archive so that the gorilla3d-v1-5 folder lies in one of the skill directories of Claude Code:

  • For one project: <your project>/.claude/skills/gorilla3d-v1-5/ Recommended if you have projects with different Gorilla3D versions. You can also commit the folder to your repository, so every developer of the team uses the same documentation.
  • For all projects: %USERPROFILE%\.claude\skills\gorilla3d-v1-5\ on Windows, ~/.claude/skills/gorilla3d-v1-5/ on macOS and Linux.

Make sure SKILL.md is directly inside the gorilla3d-v1-5 folder and not in an additional subfolder created by your unzip tool.

Start a new Claude Code session afterwards. Claude now uses the skill automatically when you work with Gorilla3D. You can also call it explicitly with /gorilla3d-v1-5.

Install in the Claude app (Desktop and claude.ai)

Open Settings, go to the skills section (under Capabilities) and upload the ZIP file as it is. Code execution must be enabled for skills to work. The skill is then available in all your chats.

Updating

When you update Gorilla3D, download the skill of the new version and remove the old one. Several installed Gorilla3D skills of different versions confuse the assistant, because it cannot know which version your project uses.

llms.txt for other AI tools

For assistants without skill support, the documentation is available in the llms.txt format:

File Content
https://docs.gorilla3d.de/llms.txt Index of the latest version, every page with a short description and a link to its Markdown source
https://docs.gorilla3d.de/llms-full.txt Complete documentation of the latest version in one file
https://docs.gorilla3d.de/llms-v1.5.txt Index of a specific version
https://docs.gorilla3d.de/llms-full-v1.5.txt Complete documentation of a specific version

How to use them depends on the tool:

  • Tools with documentation indexing (e.g. Cursor): add https://docs.gorilla3d.de/llms-full-v1.5.txt as a documentation source.
  • Assistants with web access: give them the link to the index file, they can fetch single pages from there.
  • Chatbots with file upload: upload llms-full-v1.5.txt, or single Markdown files from the references/ folder of the skill ZIP.

llms-full is large. If your tool has a small context window, prefer the index or upload only the pages you need.

Tips for working with an AI assistant

  • Name the component. "Add SSAO to my TGorillaViewport" leads the assistant to the right page faster than "make the scene look better".
  • Ask it to check the documentation. For example: "Look up TGorillaParticleEmitter in the Gorilla3D docs and create a snow effect."
  • Review the result. The documentation reduces mistakes, but does not prevent them. Compile and test generated code as usual.
  • Report gaps. If the assistant repeatedly gets something wrong, the documentation is probably unclear at that point. Let us know through our support channels.