Tavotto
AI drew your research figure. Tavotto makes it publication-ready: edit matplotlib figures on a canvas, lay out in mm, check journal rules. Free, open source.
翻譯準備中
尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證ui.artbloom — the living library of interfaces: catalog site, registry API and install CLI.
翻譯準備中
取自儲存庫 README
正在載入完整 README。 以下為已儲存的摘錄。
The living library of interfaces — production-ready React templates and animations, browsable on the web and installable with one command.
• the site (repo root) — Next.js 16 App Router app that renders the catalog and serves the registry API at /r/*
• the CLI (cli/) — the ui.artbloom npm package that reads that registry and writes files into a user's project
.env.local is required for local CLI testing:
Registry payloads declare binary assets as absolute URLs. Without that variable they point at the production origin, and a CLI install running against localhost cannot resolve them.檢視完整 README ↗The living library of interfaces — production-ready React templates and animations, browsable on the web and installable with one command.
Two things live in this repo:
/r/*cli/) — the ui.artbloom npm package that reads that registry and writes files into a user's projectnpm install
npm run dev # http://localhost:3210
.env.local is required for local CLI testing:
NEXT_PUBLIC_SITE_ORIGIN=http://localhost:3210
Registry payloads declare binary assets as absolute URLs. Without that variable they point at the production origin, and a CLI install running against localhost cannot resolve them.
npm run typecheck
npm run build
| Path | What |
|---|---|
app/(site)/ | catalog, item pages, docs, legal, auth screens |
app/(bare)/preview/[name]/ | full-page template preview, no site chrome |
app/r/[name]/ | registry payload — one JSON per item |
app/r/asset/[...src]/ | binary asset streaming for registry items |
registry/ | the actual source of every published item |
lib/registry/ | manifest, schema, source reader |
lib/brand.ts | every user-visible name and URL, derived from brand.json |
cli/ | the published npm package |
brand.json is the single source of truth for the name, domain, npm package and social links. Nothing else hard-codes them.
Every item is a shadcn-compatible static payload at /r/{name}.json:
files[]assets[] as a same-origin URL plus a byte count, streamed to disk one at a time by the CLI/r/registry.json is the index. /schema/registry-item.json is the JSON Schema. Both are prerendered at build time, so adding an item means adding it under registry/ and to the manifest — there is no database.
cd cli
npm install
npm run build # tsc -> dist/
The package is ui.artbloom; the executable it installs is artbloom (a dotted bin name is unrunnable from cmd.exe, which reads everything after the last dot as a file extension). npm resolves the package's single bin, so npx ui.artbloom add <name> works.
The default registry the CLI talks to is taken from homepage in cli/package.json. Override per-invocation with --registry.
npx ui.artbloom add morphogen-wordmark
npx ui.artbloom list --kind templates
npx ui.artbloom info cinematic-supercar
The site is a stock Next.js app — next build prerenders the whole catalog plus every registry payload and asset route, so it runs on any host that supports Next.js. The production deployment is hosted on Vercel.
MIT for the site and the CLI. Items under registry/ carry their own third-party asset licenses where applicable — see the LICENSES.md / LICENSE.txt files alongside those assets.