superlore

Author and edit content into an existing superlore knowledge base — "vibe your docs". Turns intent ("add a page about X", "document our onboarding", "make a roadmap") into well-structured MDX with dual-representation components (cards, timelines, boards, entity cards, tables, a Canvas), so humans get a clean page and agents get a typed knowledge face from one source. Use when adding, writing, editing, or restructuring pages, components, or a Canvas in a superlore KB.

Prepare best-in-class release notes for a superlore package, KB, or product — every time, the same way. Gathers what changed since the last release, classifies it (breaking / new / improved / fixed / security), writes developer-grade migration notes for breaking changes and usage notes for new features, decides whether the release is recommended to upgrade, scripts a 30–60s release reel, writes a dual-representation Release entry in the docs changelog, and cuts a GitHub Release that links back to that changelog. Use whenever someone says "cut a release", "prepare release notes", "what changed since the last version", "write the changelog entry", or "draft the GitHub release".

Stand up a new superlore knowledge base end-to-end — the "Make me a docs using superlore" flow. Greets the user, asks the few core questions with AskUserQuestion (company KB vs product docs; auth-protected vs public), runs the `superlore` CLI to scaffold, writes `superlore.json`, configures the MCP, seeds starter content, and narrates every step. Use whenever someone asks to create / scaffold / set up / start a new superlore KB, wiki, docs site, or "knowledge base for my agents", or says "make me a docs using superlore".

Migrate an existing docs site or a set of Markdown/MDX files (Mintlify, Docusaurus, Fumadocs, Nextra, GitBook, plain .md — any framework) into a superlore knowledge base. First produces a detailed migration PLAN authored as a superlore doc (with a Canvas of the migration) that the user reviews and comments on in the editor preview or the Viewer; on approval it converts every page to superlore MDX with dual-representation components, verifies the build + key pages with Playwright, and writes a post-migration summary doc with screenshots and per-item status. Use when someone wants to move / convert / port / migrate their docs to superlore, or says "migrate my Mintlify/Docusaurus/markdown docs to superlore".

Author rich, well-structured superlore Canvas diagrams — the `superlore-canvas` block in MDX that renders as a FigJam-grade interactive whiteboard AND a typed knowledge graph. Use whenever creating or editing a visual, diagram, whiteboard, board, architecture map, flow, mind-map, or brainstorm in a superlore knowledge base, or when asked to "visualize", "draw", "diagram", "map out", or "whiteboard" a concept.

Register a superlore knowledge base's MCP server with the user's Claude (or other MCP client) so their agent can read the corpus directly — search, get_page, list, navigate, get_component_data. Configures it at the USER level via `claude mcp add` (or the client's mcp.json). ALWAYS asks permission before modifying the user's Claude config, and ASKS for the URL / any credential / any missing detail rather than guessing. Use when someone wants to connect, add, hook up, or point their agent / Claude at a superlore KB or its MCP.

Get a superlore knowledge base live. superlore Cloud (managed hosting, SSO, team features) is in private beta — this skill guides the user to the waitlist, and gives the full self-host / Vercel manual path so they can ship today for free. Use when someone asks to deploy, publish, host, or "put my superlore docs online", or runs into `superlore deploy`.