figma-to-doc From Figma
Read design files, annotations, and comments. Extract individual frames as inline screenshots and turn them into documented flows and business rules.
Lore.
Claude Code plugin
Turn designs, briefs, and living products into documentation that lasts.
Lore is a reusable, product-agnostic documentation factory for Claude Code — the same skills, review subagents, and enforcement hooks, maintained once and consumed everywhere.
/plugin marketplace add hamidpl/lore/plugin install lore@lore-marketplaceWhy Lore
Documentation rots, and every team rebuilds the same process.
Screens change, briefs drift, the live product moves on — and the docs quietly fall behind. Most teams reinvent their own writing rules, review steps, and folder conventions from scratch. Lore packages that whole methodology once: install the plugin and every repo inherits the same skills, the same Definition of Done, and the same guardrails.
Three ways in
Start from whatever input you already have.
Pick the source that matches your material. Each path is a guided skill that reads the input, asks the right questions, and writes structured docs.
brief-to-doc From a brief
Work from a PRD, epic, or user story. Infer scenarios from acceptance criteria and log every clarification so gaps are explicit, not guessed.
site-to-doc From a live product
Drive a real browser to run scenarios, capture screenshots, and record exact UI text — documenting how the product actually behaves today.
How it works
From empty repo to published docs in four moves.
- 1
/lore:initScaffold
Answer three questions — product name, language, and whether to add a Docusaurus viewer. The docs layer and rules are generated for you.
- 2
figma · brief · siteGenerate
Run the skill that matches your input. It collects sources, asks clarifying questions, and writes structured documentation.
- 3
doc-reviewerReview
Validate every document against the Definition of Done before delivery — links, image paths, scenarios, and language are all checked.
- 4
buildDeploy
Ship Markdown-only docs, or build the static site and deploy the output to any host.
What you get
A documentation factory, not just a template.
Blocking enforcement hooks
Deterministic checks run on every file write — image paths, required frontmatter, and tooling leaks are caught before they reach the docs. A second family checks the evidence: a source claimed but never fetched blocks delivery.
A Definition of Done
A read-only validator subagent audits each document against the rules and returns a pass/fail report — run automatically before delivery.
Multilingual & RTL ready
Right-to-left languages get a self-hosted Persian font and proper layout out of the box — the same engine that powers this site’s documentation.
Maintained once, propagated everywhere
Methodology lives in the plugin. Fix it once and every repo picks up the change with a single plugin update.
An optional Docusaurus viewer
Keep Markdown-only docs, or add a browsable site whenever you want — the framework is fetched fresh, with RTL styling when needed.
Free QA on the side
Documenting a live product surfaces real defects; Lore consolidates what it observes into structured bug drafts you can act on.
Quick start
Two commands to install, three questions to begin.
Install (inside Claude Code)
/plugin marketplace add hamidpl/lore/plugin install lore@lore-marketplaceBoth steps are idempotent. Then enable Lore for your project.
Scaffold your project
/lore:init/lore:init asks for a product name, a documentation language, and whether to add a Docusaurus viewer — then scaffolds everything without overwriting your files.
The docs for this very site are built with Lore.
Read the documentation →