For AI Agents
KICK’s documentation is published in machine-readable form so an agent can load the whole project context in one or two requests.
Endpoints
| URL | Content | Use case |
|---|---|---|
/kick/llms.txt | Compact project summary: APIs, runtime model, key references | Cheap orientation |
/kick/llms-full.txt | Every documentation page concatenated into one file | One GET = full project context |
{page}.md | Clean Markdown for a single page | Fetch one topic |
Markdown output
Every page is served as Markdown next to its HTML. Leaf pages append .md to
the page path; sections append index.md:
/kick/docs/installation/ → HTML
/kick/docs/installation.md → Markdown
/kick/docs/reference/ → HTML
/kick/docs/reference/index.md → MarkdownContext menu
Every documentation page has a context menu in the top-right with Open in ChatGPT and Open in Claude. Both pre-load the page’s Markdown URL, so the model reads the page directly instead of relying on training data.
IDE coding agents
AGENTS.md in the repository root is auto-discovered by IDE coding agents. It
carries the rules that matter when changing code: the required task workflow,
framework constraints, design constraints, traceability requirements, and the
local make targets.
For documentation work, use the dedicated skill at
.agents/skills/documentation-hard-rules/SKILL.md and follow the
Documentation Standards.
Regenerating
make generatehack/gen-docs.sh rewrites llms.txt, rebuilds llms-full.txt from every
Markdown file under docs/content/docs/, and publishes a copy to
docs/static/ so the site serves it. make docs-gen-check fails the build when
the generated files drift from the sources.