Serve the figquery skill bundle to Cursor only - #97
Open
gjethwani-figma wants to merge 1 commit into
Open
Conversation
Adds skills-figquery/, a parallel skill tree carrying the figquery variant of the guidance, and points .cursor-plugin/plugin.json's `skills` field at it. That field overrides Cursor's default skills/ discovery, so Cursor loads the new tree and nothing else in the repo moves. Every other client is untouched. Claude Code reads .claude-plugin/plugin.json, which declares no `skills` field and so falls back to skills/. awesome-copilot pins its own ref. gemini-extension.json declares no skills at all. Both trees hold the same 14 skills under the same names, so slash commands and skill descriptions are identical either way. Only the guidance content differs. Generated from figma-plugin-fig-query at figma/figma HEAD, limited to that plugin's sync_allowlist.json (12 skills). figma-implement-motion and figma-use-motion are outside the fig-query allowlist and are copied from skills/ unchanged, so the skill set stays at 14. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
gjethwani-figma
force-pushed
the
gjethwani/cursor-figquery-bundle
branch
from
September 1, 2026 21:43
90c1843 to
e3bf0ca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rolls the figquery skills out to Cursor, and only to Cursor, without changing what any other client gets.
How it works
Cursor's manifest has a
skillsfield that takes an explicit path and overrides the defaultskills/discovery. That field is the seam. This PR addsskills-figquery/and repoints it:Everything else is untouched:
.cursor-plugin/plugin.json→skills-figquery/.claude-plugin/plugin.json, noskillsfield, defaults toskills/.github/pluginentry ingithub/awesome-copilot, pinned to its own refgemini-extension.json, declares no skillsInvisible to users
Both trees hold the same 14 skills under the same names. Slash commands and skill descriptions are identical either way, so a Cursor user sees the same
/figma-usethey saw yesterday. Only the guidance content differs. Verified that everyname:in frontmatter matches between the two trees.Provenance
Generated from
figma-plugin-fig-queryatfigma/figmaHEAD, limited to that plugin'ssync_allowlist.json(12 skills).maintainers.ymlandevals/are excluded, matching the existing sync.figma-implement-motionandfigma-use-motionare not in the fig-query allowlist, so they are copied fromskills/unchanged. That keeps the set at 14 rather than silently dropping two skills from Cursor.Sourced from committed HEAD, not the local working tree, which has unrelated WIP in that plugin.
What this does not do
Installed Cursor plugins pin to the commit they were added at and do not auto-update. This reaches new installs immediately and existing users whenever they next update the plugin. It cannot convert an already-installed user on its own.
Follow-up
mcp-sync-skillsinfigma/figmastill writes onlyskills/. It needs a second pass readingfigma-plugin-fig-queryintoskills-figquery/, or the next sync will leave this tree stale. Not in this PR.