feat(skills): Add figma-changes skill to pf-figma plugin#25
feat(skills): Add figma-changes skill to pf-figma plugin#25kaylachumley wants to merge 1 commit intomainfrom
Conversation
Adds a comprehensive skill for tracking Figma design updates and generating code update checklists. The skill: - Fetches Figma version history via API - Generates three types of reports: design changelog, release notes, and code update checklist - Cross-references GitHub issues from patternfly-design-kit and chatbot repos - Categorizes updates by status (code update needed, design-only, needs verification) - Creates token-focused checklists (color, spacer, dimension tokens) for developers - Includes reference documentation and helper scripts This skill helps PatternFly maintainers keep code in sync with Figma design updates. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
kaylachumley
changed the title
kaylachumley
changed the title
jpuzz0
left a comment
jpuzz0
left a comment
There was a problem hiding this comment.
Just 1 non-blocking suggestion. If you want to leave as-is, let me know and we can merge. Otherwise I'll wait till the comment is addressed.
| @@ -0,0 +1,265 @@ | |||
| --- | |||
There was a problem hiding this comment.
nit: At 265 lines, the three report templates are the main source of length. Could these be moved to examples/ or references/? You already have examples/sample-output.md which demonstrates the format well.
There was a problem hiding this comment.
yes they can be moved! not sure how to do that though @jpuzz0 Sorry for the late response, I was on PTO
There was a problem hiding this comment.
No worries! Here's a prompt you can give Claude or Cursor in the repo to do it for you:
In plugins/pf-figma/skills/figma-changes/SKILL.md, extract the three report templates into a separate file called `report-templates.md` in the same directory. Replace them in SKILL.md with a link to the new file.
| @@ -0,0 +1,267 @@ | |||
| #!/usr/bin/env node | |||
There was a problem hiding this comment.
Not all users will have Node.js installed, and if they don't, this will fail silently with command not found. Adding a runtime check at the top would help — something like:
#!/bin/bash
command -v node >/dev/null 2>&1 || { echo "Error: This skill requires Node.js." >&2; exit 1; }Or you could wrap the Node call in the bash extract script that already exists. I'll be updating CONTRIBUTING-SKILLS.md separately to clarify our policy on scripts in skills.
2 participants
Adds a comprehensive skill for tracking Figma design updates and generating code update checklists. The skill:
This skill helps PatternFly maintainers keep code in sync with Figma design updates.