v0.3.2 — npm shows the English README again

Packaging fix: npm was serving the Chinese translation as the package README.

Why: npm auto-detects readme* files at the package root and picked README.zh-CN.md (the last match), so npmjs.com rendered Chinese while GitHub rendered English. Registry metadata confirmed it: every release from 0.2.0 onward reported readmeFilename: README.zh-CN.md.

Fix

• The Chinese translation now lives at docs/README.zh-CN.md — still shipped in the tarball, with language links updated in both directions.
• package.json declares "readmeFilename": "README.md" as a belt-and-braces hint.
• Registry metadata now reports readmeFilename: README.md and serves the English README.

No code or behaviour change.

v0.3.1 — README refresh for the pi package

Documentation-only release: the package contents are identical to 0.3.0 apart from the README, so npm install / pi install behaviour is unchanged.

README

• The subtitle now names both entry points: a CLI for shell-only agents and a pi package with one compact tool.
• Added badges: pi-package (links to the pi.dev gallery listing) and the latest GitHub release.
• Added a three-step figma(...) usage example (screens → node → images).
• Added Node guidance: upstream figma-developer-mcp declares engines: >=20.20.0, while the code paths used here are tested on Node 18.20 in CI.

Published to npm as figma-bridge-cli@0.3.1.

v0.3.0 — pi package (one figma tool + skill)

figma-bridge is now a pi package — same package, same CLI, plus native pi support.

pi install npm:figma-bridge-cli   # adds one `figma` tool + the figma-bridge skill
npm i -g figma-bridge-cli         # unchanged: shell-only agents, CI, scripts

Added

• One figma tool with mode: screens | node | images — not a tool per operation, because tool schemas are a context tax paid on every turn.
• skills/figma-bridge/SKILL.md shipped inside the package. pi only discovers skills/<name>/SKILL.md, so the old root-level SKILL.md never loaded.
• pi manifest, pi-package keyword, and a gallery preview image for https://pi.dev/packages.
• Output truncation through pi's own helpers, with a conservative local backstop when pi is not present.

Packaging

• typebox is a runtime dependency (the extension imports it statically); pi core is an optional peer, so CLI-only users never pull an agent runtime.

Verified

• 69 tests; CI green on Node 18/20/22; end-to-end in real pi — the tool call returns live Figma data and the skill appears in the system prompt — both from a local path and from the published npm tarball.

Positioning, stated honestly: compact output, caching, truncation-with-spill and image export are not unique to this project (@pi-stef/figma and @bigmints.com/pi-figma-bridge ship those too). What this project adds: it is agent-agnostic, it ships its guidance as a skill, and its benchmarks are published and reproducible.

v0.2.1 — hardening, tests, CI, honest benchmarks

Backfilled release: npm 0.2.1 was published before this tag existed. It is the hardening release that made the project honest about its own claims.

Fixed

• -o short flag was documented but ignored — figma-bridge images … -o ./assets silently wrote to ./figma-assets. Short flags now parse everywhere (-o, -h, -v), and --help / --version exit 0.
• Path-like fileKey / nodeId are rejected before touching the filesystem (the cache directory could previously be escaped with ../../..), and a failed images call no longer leaves an empty directory behind.
• screens no longer prints a meaningless (0 children) on every frame.
• Cache: when the lastModified check fails (offline, rate-limited, lost permission) the local copy is served and labelled (cache hit, unverified) instead of failing. FIGMA_BRIDGE_CACHE_DIR overrides the cache location.
• The npm package now ships BENCHMARKS.md and assets/demo.gif — both README links were broken on npmjs.com.

Added

• node:test suite plus GitHub Actions CI on Node 18/20/22.
• bench.sh no longer deletes ~/.cache/figma-bridge: it uses an isolated temp cache and prints the measured metadata RTT.

Corrected

• BENCHMARKS: the batch-mode claim (0.18 s / ~20×) was a harness artifact — one inherited stdin redirect meant rounds 2–3 benchmarked an empty script. Re-measured: 1.82 s, ~2.3× versus three separate MCP calls.

Install: npm i -g figma-bridge-cli@0.2.1

v0.2.0

• Full Figma URLs accepted in all subcommands (no manual fileKey/nodeId extraction)
• Output compaction: default absolute-positioning layout and duplicate TEXT names omitted
• Benchmarks refreshed (node depth1 layout+text: 1783B vs 3015B via MCP bridge, −41%)
• package.json prepared for npm (bin/files/description)

v0.1.0

First release: progressive Figma design-data CLI for shell-only agents. screens/node/images subcommands, --fields presets, lastModified caching, nodejs batch mode, SKILL.md for agent integration.