メニュー
Release workflow — release-please, npm publish, server.json version sync, and MCP registry publishing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Complete Figma REST API reference — all endpoints, tier levels, auth, geometry parameters, and rate limits.
Design token extraction pipeline — frequency counting, semantic naming, token replacement, and varRef stripping.
How to register new MCP tools — tool object pattern, Zod schemas, handler conventions, and conditional registration.
SVG vector generation from Figma VECTOR nodes — caching, path merging, bounds calculation, and disk writing.
| name | release-process |
| description | Release workflow — release-please, npm publish, server.json version sync, and MCP registry publishing. |
I know the release process for the Figma-Context-MCP npm package.
Push to main branch triggers .github/workflows/release.yml.
Release Please (googleapis/release-please-action@v4)
release-please-config.json (node release-type, bump-minor-pre-major)package.json and .release-please-manifest.jsonCHANGELOG.mdIf release created:
pnpm type-checkpnpm buildpnpm publish with NPM_CONFIG_PROVENANCE=trueserver.json version with jqmcp-publisher CLIpackage.json — version field (e.g., "0.28.1")server.json — version field (e.g., "0.14.0") — sync'd by release workflow.release-please-manifest.json — {".": "0.28.1"} — updated by release-pleaserelease-please-config.json — release-type: node, changelog-path, bump-minor-pre-majorserver.json — MCP registry manifest (name, description, packages, env vars)Use this when: