尚未检测到更新。GitHub 发布版本后会显示在这里。
按最近已完成的 8 小时观测回合间的 GitHub 星标增量排序
SUPRA-Tex: reference-aligned 3D texture generation from a single image, with relightable PBR materials for image-to-3D assets and existing meshes.
翻译准备中
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权，自行管理介绍，无需管理员批准。
登录并生成验证文件，在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件，即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录，将前往登录页面。登录后请回到此处，再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify，即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗Turns a "dead" hall PDF into a live map where an event designer places their catalog,
producing three outputs from one source of truth — client visualization, placement map,
packing list — plus a price quote. See docs/ for requirements (01) and
architecture (02).
Next.js (App Router, TS, Tailwind 4) · Konva.js (2D studio) · pdf.js · Drizzle + Postgres.
Web, RTL/Hebrew. See docs/02 for the ADRs — notably ADR-4: the Design Document is
pure data (lib/design-document/), and the canvas / PDF / 3D are all renderers of it.
app/ Next.js routes (UI + API)
lib/db/schema.ts data model — every table carries organizationId (ADR-2)
lib/design-document/ ADR-4 keystone: pure document types + the single actions layer
docs/ requirements + architecture (source of truth)
cp .env.example .env.local # DATABASE_URL for local Postgres
docker compose up -d # local Postgres (needs Docker Desktop)
npm run db:migrate # apply drizzle/*.sql (NOT db:push — see below)
npm run dev # http://localhost:3000
Other: npm run check:actions (reducer/undo-redo self-check), npm run db:studio,
npm run build.
The database is on generated migrations, not db:push. Since August 2026 there is a hosted
database with data worth not losing, and push reaches a schema without leaving a record of how —
which is fine until two databases have to agree.
# 1. edit lib/db/schema.ts
npm run db:generate # writes drizzle/NNNN_<name>.sql + a snapshot
npm run db:migrate # applies it locally
# 3. commit the .sql, the snapshot AND drizzle/meta/_journal.json together
db:push still exists for throwaway experiments against a scratch database. Do not point it at
Neon: it would reach the same schema while leaving __drizzle_migrations claiming otherwise, and
the next real migration would then be generated against a snapshot that no longer describes
anything. Production is applied by running db:migrate with DIRECT_URL set to Neon's direct
host — deploying does not run migrations on its own.
Phase 1, step 1 — scaffold + data model + design-document/actions layer. Next: catalog, then the 2D studio. Build order in docs/02 §7.