Lerret
Your project is a folder of React components. Lerret renders it.
Two architectural choices make Lerret different:
The folder is the project. No save button, no design mode, no proprietary file. The .lerret/ directory on disk is the project — Lerret only reflects what’s already there. Git treats it like any other folder. If Lerret disappears tomorrow, you still have a working set of React components.
The format is React. Because every asset is real React, every LLM already knows how to edit it — just files an AI was trained on millions of times over. Lerret’s own AI comes two ways: the in-studio dock (your own key, or local Ollama) and /lerret, installed as a Claude Code plugin (keyless, Claude Code only).
Everything else — git-native versioning, AI-fluent editing, no vendor lock-in — falls out for free. Pan-and-zoom artboards, sub-second hot reload, headless PNG/JPG export.
Try it now
npm create lerret@latest my-canvas
cd my-canvas
npx @lerret/cli@latest devThe studio opens in your browser. Save any .jsx file under .lerret/ and the canvas re-renders in under a second.
What’s in the box
- Studio — pan-and-zoom canvas, per-artboard error boundaries, in-place editors for component data + config.
- Built-in AI — a brand-aware agent in the dock that designs and edits your assets, using your own provider key (OpenAI, Anthropic, OpenRouter) or a fully-local Ollama. Browser-direct, no Lerret backend.
- Claude Code plugin —
/plugin install lerret@belikely-united, then one/lerretcommand authors, previews, and exports assets with your own Claude as the brain. No API keys. - CLI —
npx @lerret/cli@latest devopens a folder as a live canvas;npx @lerret/cli@latest exportheadlessly renders to image files (PNG, JPG, structured ZIP). - No backend — files read and written locally; no upload, no sync, no account.
- Three deploy modes — local CLI, hosted (browser File System Access API), or self-hosted static studio.
What’s next
- Getting Started — install and render your first canvas.
- Concepts — the folder-canvas model, page groups, variants, the four-tier prop cascade.
- Authoring Assets — JSX components, props schemas, data files, fonts, Markdown.
- AI in the Studio — the built-in brand-aware agent: prompt the dock to design and edit your assets.
- Editing with AI Tools — the Claude Code plugin, plus per-project integrations for Cursor, Copilot, and AGENTS.md agents.
- Examples — sixteen complete, runnable assets — OG cards, YouTube thumbnails, component showcases, more.
- CLI Reference —
devandexportcommands.
Community & support
Lerret is built openly. Here’s where to find us:
| Channel | When to use it |
|---|---|
| GitHub Discussions | Questions, ideas, show-and-tell, “how do I…?” |
| GitHub Issues | Bug reports, feature requests, regressions |
| Source repo | Code, releases, contributing guide, “good first issue” labels |
| npm | The @lerret/cli, @lerret/core, and create-lerret packages |
| X (@sooryagangaraj) | Maintainer’s account — release notes, project updates |
Email — oss@belikely.com | Security disclosures, partnerships, anything not appropriate for a public issue |
The project is MIT licensed and built openly by Belikely United . Contributions of every size are welcome — see the contributing guide for the workflow.