mesh-avatar-studio
일러스트를 코딩 에이전트와 로컬 편집기로 2D 메쉬 애니메이션 아바타로 변환
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기adamforrester/prism3
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
A design-tokens repository with two layers: a legacy hand-built token set and a
dependency-free TypeScript generation engine that reproduces it and generalizes to new
brands. The engine is the active surface; the hand-built layer is its regression target.
Live dashboard — — the engine running client-side: edit a
brand's levers and watch the ramps, the component preview and the per-mode contrast contracts
re-resolve.README 전문 보기 ↗A design-tokens repository with two layers: a legacy hand-built token set and a dependency-free TypeScript generation engine that reproduces it and generalizes to new brands. The engine is the active surface; the hand-built layer is its regression target.
Live dashboard — https://prism3-ds.vercel.app/ — the engine running client-side: edit a brand's levers and watch the ramps, the component preview and the per-mode contrast contracts re-resolve.
This is a signpost. The durable state — status, decisions, architecture — lives in the docs linked below; this file points, it doesn't restate. For agent conventions read
CLAUDE.md; to pick up work, start withCONTRIBUTING.md.
| Path | What it is |
|---|---|
packages/engine/ | The generation engine — a brand is a small validated input that expands into a full token tree, AI metadata, and platform outputs (DTCG + Figma). Buildless and dependency-free; consumed by name as @prism3/engine. Start here for engine work. See packages/engine/README.md. |
docs/ | The design record — the numbered design docs (the architecture spec, the decisions log, the open questions) plus superpowers/ working notes. |
reference/ | The legacy hand-built tokens — Prism2 (nbds.pds.*) and New Balance, in two parallel formats (Figma variable export + DTCG). The engine's regression target, not a build output. |
apps/studio/ | The theme studio — a browser host over the engine's shared lever/preview contracts, deployed at the link above. See apps/studio/README.md. |
apps/plugin/ | The Figma plugin — the write host over the same engine core, split across Figma's two isolated contexts (main thread + UI iframe) with a typed message bridge between them. See apps/plugin/README.md. |
apps/tokenpress/ | TokenPress — the Figma plugin that exports Figma Variables, Text Styles, and Effect Styles out to DTCG. It runs the opposite direction from the engine, and it ships publicly in the Figma Community. Ported in whole rather than rewritten; it still has its own emitter and shares no code with packages/engine/. See apps/tokenpress/README.md. |
packages/tokens/ | The consumability gate — a stock Style Dictionary build over the emitted DTCG, kept deliberately naive so it answers whether a stranger could consume the output without code from us. See packages/tokens/README.md. |
skills/ | The shipped skills — prism3-theme (authoring a brand) and prism3-consume (building UI from generated tokens) and prism3-rebind (moving an existing Figma file onto Prism3), for an agent working with Prism3; and prism3-build-component (authoring a new component definition), for an agent working on the engine. Gated by lint-skills.ts, because a skill describing a stale API is worse than no skill. |
tools/ | Measurement harnesses — runnable and committed. exporter-comparison/ runs both DTCG exporters over the same brand and classifies every difference: the measurement (compare.ts) reports and always exits 0, while the assertable subset of it (gate.ts) is a CI gate. Kept as two files, because a tool answers a question and a gate asserts an answer. nest-exposed-cost/ measures what a nest-exposed nested part would cost the parent that exposes it — a measurement only, since nobody has decided what the ceiling ought to be. |
The engine core is buildless — self-contained TypeScript run via tsx, with no build step and
no dependencies of its own (CI runs it on Node 22):
npx tsx packages/engine/test.ts # unit tests — color math + extreme-brand contracts + design.md/CLI
npx tsx packages/engine/nb-regression.ts # regression: generated tokens vs the real New Balance set
npx tsx packages/engine/emit-dtcg.ts # emit the DTCG token tree; validate every alias + mode contrast contract
npx tsx packages/engine/emit-figma.ts # emit the Figma import artifact (out/figma/<brand>/)
The full command list (CLI, visualize, the emit-* contract writers) is in
packages/engine/README.md.
The surfaces around that core — apps/studio/, apps/plugin/,
packages/* — are npm workspaces that bundle it, so they do need an install:
npm install # from the repo root — resolves every workspace
npm run dev -w @prism3/studio # esbuild dev server on http://127.0.0.1:5173
npm run build -w @prism3/studio # bundle to apps/studio/dist/
apps/studio/README.md has the rest — what each stage of the shell does,
and the deploy contract behind the live link above.
Validation here isn't a linter — it's a set of contracts every change must keep green before
merge. .github/workflows/ci.yml is the authority on the full list and
runs every one of them on each PR; what follows is a summary of what they cover, not the checklist:
{…} alias resolves and every per-mode contrast contract passes; committed out/* has not drifted; the token-name contract has not broken.studio and plugin typecheck and build (esbuild does not typecheck), the plugin's Figma-API shim tests, and the studio chrome held to its own contrast floors and class-name rules.out/*, the emitted contracts, the shipped skills, this file, and the built web bundle.A PR states their results (see the PR template); the runnable
checklist lives in CONTRIBUTING.md §3.
CONTRIBUTING.md — the workflow, the gates in full, how to brief an agent on this repo, and where each kind of durable state lives.docs/00-progress.md — status, the decisions log, and prioritized next steps (read this for handoff).docs/07-e2e-journey.md — the designer ↔ developer ↔ agent pipeline and the portable-core architecture.docs/10-figma-materialization.md — the emit-figma contract (the Figma-target shape).docs/01-token-architecture.md — the architecture spec + Theme Schema contract.