Skip to main content

Lore

Lore is a reusable, product-agnostic documentation factory packaged as a Claude Code plugin. Install it in any documentation repository to get the same authoring skills, review subagents, and blocking-rule enforcement hooks — maintained once, consumed everywhere.

:::info Stable Lore follows semantic versioning: breaking changes to commands, templates, or conventions land only in a major release. See Versioning to pin a fixed tag. :::

The problem it solves​

Screens change, briefs drift, and the live product moves on — while the docs quietly fall behind. Most teams reinvent their own writing rules, review steps, and folder conventions from scratch, in every repo.

Lore packages that whole methodology once. Install the plugin and every repository inherits the same skills, the same Definition of Done, and the same guardrails. Fix something in the plugin and every repo picks up the change with a single update.

Three ways to author​

Start from whatever input you already have. Each path is a guided skill that reads the source, asks the right questions, and writes structured documentation.

SourceSkillUse it when
Figma designslore:figma-to-docYou have design files, mockups, or annotations
Briefs / PRDslore:brief-to-docYou have written requirements or user stories
A live productlore:site-to-docYou want to document how the product actually behaves

Validate the result against the Definition of Done with lore:doc-reviewer before delivery.

How it fits together​

Lore carries only the product-agnostic methodology. Everything product-specific — trusted sources, user roles, document structure, language — lives in the consuming repository's own configuration. That division of responsibility is what lets one set of skills serve every product.

An optional Docusaurus viewer turns the Markdown into a browsable, multilingual and RTL-ready site — the same engine that builds the documentation you are reading now.

Where to next​