mesh-avatar-studio
일러스트를 코딩 에이전트와 로컬 편집기로 2D 메쉬 애니메이션 아바타로 변환
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기livediagram.app mono repo. Containing frontend and backend code.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A collaborative diagram editor that works without signing in. Open a link, draw, share. Real-time presence, cursors, comments, undo and redo. The canvas never sits behind an auth wall, so the friction to start is "open the link, start drawing."
Live at livediagram.app. MIT-licensed and self-hostable end-to-end.
• Marketing at / is the pitch and feature tour.
• Editor is the canvas, served at clean routes (/new, /document/, /explorer/...; no /live prefix). Guests get a per-browser identity and full persistence; signed-in users get the saREADME 전문 보기 ↗The monorepo for liveworkspace and its products, livediagram, liveplanner, livedocuments and livedesign, plus what they share.
packages/ shared by every product (@liveworkspace/*)
liveworkspace/ the platform: the liveworkspace.app site, its services (accounts, index, drive, media,
community, telemetry, status), the migrate tool, and its specs (liveworkspace/docs/specs)
livediagram/ livediagram.app
liveplanner/ liveplanner.app
livedocuments/ livedocuments.app: articles, slides and infographics
livedesign/ livedesign.app: logos, wireframes and photos
docs/ how this repo is laid out, CI and deploys, and the move from the historical livediagram.app
Read docs/structure.md first: it covers what's shared, what each product keeps, and the order the sharing was done in.
Every product and the platform keeps its specs and blueprints in its own docs/specs/
(liveworkspace's are liveworkspace/docs/specs). A change updates the
spec first, then the blueprint, then the code.
One pnpm workspace and one lockfile, at the root. Node 22+, pnpm via corepack.
corepack pnpm install
corepack pnpm dev:diagram # livediagram's apps
corepack pnpm dev:planner # liveplanner's apps
corepack pnpm dev:documents # livedocuments' apps, on the 33xx ports
corepack pnpm dev:design # livedesign's apps, on the 34xx ports
corepack pnpm dev:workspace # liveworkspace.app on :3000, with its seven services behind it
corepack pnpm dev:site # liveworkspace.app's pages alone on :3000
corepack pnpm dev:accounts # the accounts API alone on :8787
corepack pnpm dev:telemetry # the telemetry API alone on :8790
corepack pnpm dev:community # the Community API alone on :8791
corepack pnpm dev:media # the media API alone on :8792
corepack pnpm dev:index # the index API (One Explorer) alone on :8793
corepack pnpm dev:status # the status Worker alone on :3010
corepack pnpm dev:drive # the Google Drive mirror alone on :3011
corepack pnpm typecheck # everything; or inside a product folder, just that product
Each product folder keeps its own scripts (cd livediagram && corepack pnpm test runs only
livediagram's tests), its own docs, and its own AGENTS.md for product-specific rules. The lint,
format, test and Next.js settings are shared (packages/oxlint-config, prettier-config,
vitest-config, next-config), so a rule changes once for every product.
Every product deploys from here, from the root .github/, to the liveworkspace Cloudflare account
each wrangler.toml pins. Staging follows main, and production is a manual gate that ships what
staging runs. A deploy builds and ships only the Workers a change reaches. The products' own
.github/ folders are inert. docs/ci.md has the details.