尚未偵測到更新。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.