Conversation
…ource Figma AI's custom-skills runtime uses a different native tool surface than the one these skills were originally authored against — search_variables, search_styles, assistant_component_search, and evaluate_script, not search_design_system / get_variable_defs. Since uploading kuat-tokens and kuat-components to Figma AI's custom skills manager, the tool references in both were corrected there; this ports those corrections back into the checked-in sources so the two copies stay in sync. kuat-tokens: - Add a "Figma AI tool mapping" section naming the four real tools. - Add a "Variable naming convention in Kuat2" section documenting the semantic/ prefix and the full rounded-* radius scale (none/sm/md/lg/xl/2xl/full) as discovered against the live library. - Replace search_design_system/get_variable_defs references throughout with search_variables/search_styles; radius-* examples renamed to rounded-* to match real Kuat2 variable names, with a Figma variable name column added to the radius-by-category table. kuat-components: - Add a "Figma AI tool mapping for component discovery" section. - Replace search_design_system references with assistant_component_search. - Name the concrete rounded-none variable in the content-card radius trap. Re-ran node skills/scripts/bundle-skills.mjs; all six figma-custom-skills files still validate under the 65,536-char limit (kuat-tokens 13,099; kuat-components 9,438 chars).
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.
Summary
Follow-up to #25 (merged). After uploading
kuat-tokensandkuat-componentsto Figma AI's custom skills manager, Figma AI's own runtime corrected the tool references in both — that runtime exposes a different native tool surface (search_variables,search_styles,assistant_component_search,evaluate_script) than the one these skills were originally authored against (search_design_system,get_variable_defs). This ports those corrections back into the checked-in sources so both copies stay in sync.Changes
kuat-tokens
semantic/prefix and the fullrounded-*radius scale (none/sm/md/lg/xl/2xl/full) as discovered against the live library.search_design_system/get_variable_defsreferences throughout withsearch_variables/search_styles;radius-*examples renamed torounded-*to match real Kuat2 variable names, with a "Figma variable name" column added to the radius-by-category table.kuat-components
search_design_systemreferences withassistant_component_search.semantic/rounded-nonevariable in the content-card radius trap.Verification
Re-ran
node skills/scripts/bundle-skills.mjs— all sixfigma-custom-skillsfiles still validate under the 65,536-char limit, no build errors:Content was verified line-for-line against the Figma-pulled copies before merging (diffed with frontmatter/footer stripped — exact match).
🤖 Generated with Claude Code