Skill: Ask the docs

Written for blit386 1.8.0. The rest of blit386.dev documents the newest engine, so an API you find there may be missing from a game pinned to 1.8.0.

Look up BLIT386 detail the project's own files do not cover, using the live documentation at blit386.dev.

When to use

Use when AGENTS.md and the docs/ folder do not answer the question - an API you cannot find, an option that is not listed, or something added to the engine after this game was created.

Read the local docs first

The guides in docs/ are already on disk, cost nothing to open, and describe the BLIT386 version this game actually pins in package.json. AGENTS.md has a table telling you which one to open. Go to the network only after that table comes up empty.

Three ways to reach the live docs

1. The blit386-docs MCP server

This project ships its configuration, so your assistant should already have it. Three tools:

• search_docs - full-text search across the whole documentation site. Give it a short query such as palette animation or gamepad deadzone. It returns page titles, URLs, and excerpts.
• get_doc_page - the full text of one page as markdown. Pass it a URL from search_docs (or a path such as /docs/guides/input) when the excerpt is not enough.
• get_docs_summary - the whole site's contents in one compact block. Reach for this when you do not yet know what to search for.

No game folder yet, or helping someone who has none? Start at https://blit386.dev/docs/build-a-game - a starter project to copy, this kit's guides and skills, and complete examples, all readable with get_doc_page. Those pages target the version printed at their top.

In Claude Code the server is configured in .mcp.json and pre-approved in .claude/settings.json (enabledMcpjsonServers), so it is on without a separate prompt once the project folder is trusted. The GitHub Copilot CLI and VS Code read that same .mcp.json. In Cursor it is configured in .cursor/mcp.json, in Antigravity in .agents/mcp_config.json, in Gemini CLI in .gemini/settings.json, in OpenCode in opencode.json, and in Zed in .zed/settings.json. In Codex it is the [mcp_servers.blit386-docs] table in .codex/config.toml, which Codex reads once the project is trusted.

2. The plain-text summary

Fetch https://blit386.dev/llms.txt for the same site summary as one plain text file. This is the fallback when the MCP server is not available. Find the page you need in it, then fetch that page.

3. Any doc page as markdown

Request a page URL with the header Accept: text/markdown and the site returns markdown instead of HTML - no navigation, no menus, far less to read:

curl -sH 'Accept: text/markdown' https://blit386.dev/docs

Notes

• The live site documents the newest BLIT386. This game pins a version in package.json, so something you find there may not exist here yet. Check the pinned version before using an API the local docs never mention, and run npx blit doctor if you are unsure what is installed.
• The docs server is read-only. It searches and returns documentation; it cannot change anything in your game.
• The source code lives at https://github.com/blit386/blit386. Go there only when the documentation itself does not answer the question.
• Found something the local docs do not cover? Write it into the "Your notes" section of AGENTS.md so nobody has to look it up twice.