Docs for AI agents
Read these docs from an AI assistant or agent. Every page has a Markdown version, and llms.txt and llms-full.txt index the whole site.
These docs are written to be read by people and by AI tools. Point your assistant at the Markdown versions below, or copy a page straight into a chat.
Markdown pages
Every page has a plain Markdown version with the same content: the title, a summary, the page URL and the date the page was last checked against the app, then the text with steps numbered, notes marked, tables kept and screenshots and videos as links.
- Add
.mdto any page URL, for examplehttps://flashboards.yaroflasher.com/docs/quickstart.md. The docs home ishttps://flashboards.yaroflasher.com/docs/index.md. - Or request a page URL with the header
Accept: text/markdown. Pages also list their Markdown version in a<link rel="alternate" type="text/markdown">tag.
Indexes for the whole site
| File | What's in it |
|---|---|
| Feature map (Markdown, JSON) | Everything you can do on FlashBoards, one line each: who can use it, whether it costs money, the docs page and the MCP/API tool. Read it to grasp the platform in one go. |
| llms.txt | Every page in sidebar order, with a one-line description and its Markdown link. Start here. |
| llms-full.txt | The full text of every page in one file, separated by rules. Use it when your tool can't follow links. |
The page menu
At the top right of each page, and again at the end of it:
- Copy page copies the page as Markdown, ready to paste into any chat.
- The arrow next to it opens more actions: Copy page link (the Markdown URL), View as Markdown, and Open in ChatGPT, Claude, Perplexity or Cursor. These open a new chat with a prompt that asks the assistant to read the page and answer your questions. You still send the prompt yourself.
Let an agent use FlashBoards
Reading the docs is one part. To let an agent work on your boards, find references or start generations, connect it over MCP or call the Public API.
For reusable local tools with optional panels, read the Customization SDK. The public guide and board-action envelope schema can be read before installation. Live extension schemas need SDK pilot access and a local-board tab; installation and invocation also need human plugin consent.