Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →awdr74100/figma-typings-audit
Upgrade @figma/plugin-typings and absorb what the new version exposes. Diffs the .d.ts between the installed and the target version (that package ships no changelog), sorts the changes into breakage / new API / silently-added fields, maps each onto the sandbox handlers, the hand-written Zod mirrors in shared, and the tool registry — then bumps the package and builds whatever the user picks.
Passed 12 of 17 test cases with the skill, and 5 of 17 without it.
and 10 more in the full report
11 fixed5 passed either way5 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We ran Stage 0 version resolution for `@figma/plugin-typings` and discovered that the installed version in `node_modules` matches the target npm version `1.135.0`. What is the immediate next step?
| Checked | Without skill | With skill |
|---|---|---|
| Reports that installed and target versions are identical. | Passed | Passed |
| Halts the process immediately without running further stages. | Missed | Passed |
The instructions your model reads when the skill loads.
Absorbing a @figma/plugin-typings release into Figwright, end to end: audit → upgrade →
implement what's worth having.
One hard ordering constraint: diff before upgrading. The audit compares the installed version
against the target, so upgrading first destroys the baseline. (Recoverable — the old version is in
git history and npm pack can still fetch it — but don't create the problem.)
Target version: whatever the user named, otherwise the latest on npm.
grep '@figma/plugin-typings' packages/plugin/package.json # the declared range
grep '"version"' packages/plugin/node_modules/@figma/plugin-typings/package.json # what is installed
npm view @figma/plugin-typings version # latest
npm view @figma/plugin-typings versions --json # how many releases are being skipped
Compare against the installed version, not the declared range — a caret range can already be satisfied by something newer than what the lockfile pinned.
If installed and target are equal, say so and stop. Don't spend tokens on the rest.
There is no other source. figma/plugin-typings ships no CHANGELOG and no GitHub Releases (the
releases API returns an empty array), and its commit messages are content-free (1.132.0,
Release v1.132 updates). The .d.ts diff is the only ground truth.
Work in the session scratchpad directory ($SCRATCH below):
cd "$SCRATCH" && mkdir -p typings-audit && cd typings-audit
npm pack @figma/plugin-typings@<installed> @figma/plugin-typings@<target> --pack-destination .
for v in <installed> <target>; do
mkdir -p "$v" && tar -xzf "figma-plugin-typings-$v.tgz" -C "$v" --strip-components=1
done
diff -rq <installed> <target> # which files differ at all — start here
diff -u <installed>/package.json <target>/package.json
diff -u <installed>/index.d.ts <target>/index.d.ts
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.