@exellix/ai-tasks-docs

Knowledge SDK for the ai-tasks-mono-repo (the Exellix AI-tasks ecosystem), built the same docify way. Install as a devDependency only.

npm i -D @exellix/ai-tasks-docs

import { aiTasksDocs } from "@exellix/ai-tasks-docs";

aiTasksDocs.listUseCases();
aiTasksDocs.getUseCaseMarkdown("run-a-task");
aiTasksDocs.getBookMarkdown("02-runtime-flow", "developers");

CLI: ai-tasks-docs list-books · ai-tasks-docs use-case <id> · ai-tasks-docs book <id> <audience>

What it documents

Books cover the ecosystem overview, the @exellix/* package map, the runTask() runtime flow, local dev & playgrounds (including HTTP execute endpoints and /_live), releasing the stack, and how agents consume this knowledge.

Human site (deployable)

The npm package is the agent knowledge SDK. The hostable static site is built separately:

cd ai-tasks-docs
npm install
npm run build:bundle   # → dist/web (and dist/bundle)
npm run docs           # local preview via docify-web on :4173

Deploy dist/web as static files (S3, Cloudflare Pages, nginx, etc.), or:

npx @x12i/docify-web serve ./dist/web --port 4173

dist/ from npm run build alone is only the TypeScript SDK (index.js / CLI) — not a website.

The docify way

Content lives under content/NN-slug/{audience}/BOOK.md with contracts in data/{site,catalog,use-cases}.json and product pages in site-pages/. scripts/build-knowledge.mjs embeds packs into the SDK; scripts/build-bundle.mjs emits the human site. Broken use-case reading paths fail the build.

This is the docs of the ai-tasks ecosystem — a devDependency knowledge package, not a production runtime dependency.