docs(skills): pine-figma authoring skill — ground AI-authored Figma on Pine - #793
Merged
Merged
Conversation
✅ Deploy Preview for pine-design-system ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
pixelflips
approved these changes
Aug 13, 2026
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
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.
Description
Companion to the
pinecode skill (#789). That skill grounds AI codegeneration on Pine; this one grounds AI Figma generation on Pine.
Motivation / context: when designers use AI to make Figmas
(
generate_figma_design, Figma Make/First Draft), the default output isdetached rectangles with hardcoded px and off-library text — it looks like
Pine but has no relationship to the system (layers show raw frames, Dev Mode
hands off CSS instead of
pds-*). We already have the read direction (CodeConnect in
libs/figma/, the Pine variables, thepinecode skill); the missingpiece was a guardrail on the author direction. This is that guardrail.
It follows the same shape as the code skill — resolve → compose → bind →
audit:
search_design_system/get_libraries; never invent a component.❖ Pine components, never draw shapes.✳ Pine stylestypography/*style; spacing/color/radius bind to Pine variables. No hardcoded px.get_variable_defs+get_design_contextflag detached instances, unbound values, and⛔ DO NOT USE(Sage/Mercury) assets; loop until clean.Notable decision —
pds-textandpds-boxlive here, not as Code Connectfiles: Code Connect attaches to a component node, and neither exists as one in
the Pine Figma file (text = text styles; layout = auto-layout + variables). That's
exactly why AI-drawn Figmas leak into px — the two primitives every screen is
mostly made of have no component to drag in. Their code relationship is carried as
a style/variable→code map in
reference/primitives.md. (See the companion PR #794which reclassifies them in
CODE_CONNECT_COVERAGE.md.)No new dependencies.
Fixes #(no issue)
Type of change
How Has This Been Tested?
search_design_systemconfirmed text =✳ Pine stylesand no Box/Text component; the⛔ DO NOT USESage/Mercury library names are the real ones returned) and against thepds-text/pds-boxcomponent APIs inlibs/core.Test Configuration:
Checklist:
Follow-up
Generalize the
/.well-known/skills/manifest generator inlibs/core/.storybook/main.js(added with #789) from the hardcodedskills/pineto enumerate all
skills/*, so this skill installs vianpx skills addtoo.Left out here to avoid touching #789's unmerged generator.