jonsoku-dev/figma-flow
Turn a product brief into traceable Figma screens, screen specifications, and frontend implementation.
Design a game campaign's custom logo, wordmark, utility icons, collectible pictograms or localized typography. Use the current brief to choose vector drawing, image-generated exploration and lettering work, place the final editable elements in the designated Figma source, and verify actual sizes and exports.
Turn any idea or brief into a canonical requirement/screen/acceptance/code/evidence graph, linked screen specifications, and frontend implementation. Use for local-only delivery, local design tokens, one registered Figma workspace with Codex-prepared tasks and local sync, selected-page developer-plugin readback-to-app scalar sync and chained edits, local developer-plugin SDK feature routing, local source/brief audits, reviewed resumption after changes, verified bundled Impeccable and design-taste-frontend sources with font-first authoring/critique, genuine image-generated role assets and same-concept game batches, text-responsive generated skins, automatic prompt-to-design skill routing for logo, icons, raster imagery, typography, collectibles and Figma semantic handoff and SSOT, a curated Korean/Japanese mobile game campaign reference library with category-specific acceptance checklists, a searchable catalog across project manifests, selected draft builds, or pinned affected-test planning and execution; honor narrower requested scope.
Install Figma Flow in Codex, connect its stable Figma workspace and Codex-prepared task list, verify actual readback, or update and repair that connection. Handles private repositories, company npm registry setup, and environments with or without Computer Use.
Use when a graph must own component design values, export them to Figma and web, import designer edits, or verify a native/web round trip.
Record a Figma Flow patch, audit missing patch history, or use observed failures to propose and verify a scoped improvement with the embedded Git-backed wiki.