agentleFS
nexoralnexoral/AxioDB/Document/AGENTS.md

AxioDB / Document

AGENTS.md35 starsChanged 9 days agoMITView on GitHub

Global rules live in ../AGENTS.md. This file only adds Document/ specifics — read the root first. Role — the public documentation site (axiodb.in) and the project's single source for AI artifacts. Vite + React, pre-rendered with vite-react-ssg, deployed to Cloudflare Pages. Dev server on 5173. React 18 · Vite 6 · vite-react-ssg (SSG) · Tailwind CSS v3 (tailwind.config.js + PostCSS) · tsx scripts · Turndown for markdown twins. This is TypeScript (.tsx/.ts) — unlike GUI/. public/llms.txt, llms-full.txt, openapi.json, feed.xml, sitemap.xml…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the four surfaces clearly separated in the prose — never blur core · Dashboard · HTTP API 27018 · TCP 27019 · MCP 27020 (native in …

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Document/ — Docs Site (Agent Instructions)

Global rules live in ../AGENTS.md. This file only adds Document/ specifics — read the root first.

Role — the public documentation site (axiodb.in) and the project's single source for AI artifacts. Vite + React, pre-rendered with vite-react-ssg, deployed to Cloudflare Pages. Dev server on 5173.

Stack

React 18 · Vite 6 · vite-react-ssg (SSG) · Tailwind CSS v3 (tailwind.config.js + PostCSS) · tsx scripts · Turndown for markdown twins. This is TypeScript (.tsx/.ts) — unlike GUI/.

Layout

src/
  data/         serverApi.ts (SINGLE SOURCE for API docs + openapi.json), changelog.ts, breadcrumbs.ts
  components/   content/ (page bodies), layout/ (Footer.tsx …), ui/
  services/, hooks/, styles/, Assets/
scripts/
  generate-seo-files.ts   prebuild: sitemap, llms.txt/llms-full.txt, openapi.json, feed.xml
  generate-markdown.ts    postbuild: markdown twins
  audit-crawler-access.mjs
public/       llms.txt, llms-full.txt, openapi.json, feed.xml, sitemap.xml, robots.txt, _headers, .well-known/
wrangler.toml Cloudflare Pages config — build output "AxioDB_Docs"

Commands

cd Document
npm run dev      # http://localhost:5173
npm run build    # prebuild → SSG build → postbuild (three steps, all run by `npm run build`)
npm run lint
npx tsx scripts/generate-seo-files.ts   # regen AI artifacts only

Hard rules

  • Single source: API reference comes from src/data/serverApi.ts, which feeds both the rendered docs and public/openapi.json. Edit the data file — never the generated openapi.json by hand.
  • src/data/changelog.ts's newest entry version must equal package.json's version.
  • Keep the four surfaces clearly separated in the prose — never blur core · Dashboard · HTTP API 27018 · TCP 27019 · MCP 27020 (native in core & Docker).
  • Tailwind v3 config style here; do not copy GUI's v4 @tailwindcss/vite setup.
  • AxioDB_Docs/ (build output), .vite/, .wrangler/ are gitignored — never commit them.

AI artifacts (regenerate, don't hand-edit where generated)

public/llms.txt, llms-full.txt, openapi.json, feed.xml, sitemap.xml are produced by the scripts above and also by the version-bump pipeline. Regenerate rather than editing generated bodies.

Version sync (this folder — many touchpoints)

  • Document/package.json → "version"
  • src/data/changelog.ts → newest entry version
  • src/components/layout/Footer.tsx → displayed version
  • index.html → JSON-LD softwareVersion
  • public/llms.txt → "Current version:" line · public/llms-full.txt → "Version:" line
  • public/feed.xml → RSS title + guid
  • src/components/content/ControlGui.tsx → versioned installer filenames (axiodb-control_<ver>_amd64.deb, ...-<ver>.AppImage)

Scripts/versionController.sh rewrites all of the above; regen artifacts with npx tsx scripts/generate-seo-files.ts.

Done for this folder

  • npm run build passes (prebuild + SSG + postbuild all green)
  • npm run lint clean
  • serverApi.ts updated (not openapi.json); AI artifacts regenerated
  • All seven version touchpoints above match root

AxioDB is an embedded database like SQLite built in pure TypeScript for Node.js, Bun, and Deno, with over 37,000 total downloads on npm and roughly 4,000 downloads each month. It solves the biggest issue with SQLite by eliminating native C bindings and node-gyp build failures across operating systems. At the same time, it fixes the limitations of raw JSON stores where you cannot run complex queries. Most alternative embedded npm packages dump everything into a single file and fail on larger datasets like 500,000 documents. AxioDB bridges this gap by providing a zero native dependency document store that handles large datasets smoothly, supports advanced queries and aggregation pipelines, and provides ACID transactions out of the box with zero compilation setup.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.