ui-color-palette-framer
Skill1 starsChanged 7 months agoMITView on GitHub
Entry point for UI Color Palette workflows targeting Framer. Use to choose between color style synchronization and visual document preview generation.
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this folder as the platform entry point for all UI Color Palette → Framer workflows.
- Very specific: line 20
If it is, use it directly — never call get_palette again.
- Distinctive: line 24
Only rebuild the palette if the user explicitly asks to change colors, preset, or themes.
- Distinctive: line 37
only then translate the workflow into MCP or plugin API operations
- Distinctive: line 39
Do not start from raw API calls.
- Very specific: line 59
When routing a SystemData-based workflow to references/generate-styles.md, pass SystemData opaquely.
- Distinctive: line 60
First: ensure the palette's primitive color styles exist — create them if missing (mandatory prerequisite)
- Very specific: line 61
Create one color style per token, named by the system name + token path (/systemName/tokenPath)
- Distinctive: line 78
create/update visual preview documents
- Distinctive: line 84
Use MCP or direct API calls as the execution layer, not as the skill structure.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UI Color Palette Framer
Use this folder as the platform entry point for all UI Color Palette → Framer workflows.
Folder structure
SKILL.mdat the root is the platform indexreferences/contains the detailed operational sub-skills
Reuse rule
Before calling any MCP tool, check whether PaletteData is already present in the conversation context.
If it is, use it directly — never call get_palette again. Confirm to the user:
Using the palette already built in this session. Generating Framer artifacts now.
Only rebuild the palette if the user explicitly asks to change colors, preset, or themes.
Structure-first rule
This platform skill is primarily a routing and orchestration layer.
The agent should:
- identify whether the user needs styles or preview first
- choose the matching file in
references/ - normalize the palette payload for that workflow
- only then translate the workflow into MCP or plugin API operations
Do not start from raw API calls. Start from the workflow structure.
Available sub-skills
references/extract-source-colors.md— extract fill colors from the current Framer selection to seed a palettereferences/extract-styles-colors.md— extract colors from Framer local color styles to seed a palettereferences/generate-styles.md— generate and update Framer local color stylesreferences/generate-preview.md— draw the palette as a swatch board on the Framer canvas (canvas rendering only, not style export)
Routing
Choose the sub-skill by user intent:
- “extract colors from selection”, “pick colors from selection”, “colors from Framer” →
references/extract-source-colors.md - “extract colors from styles”, “color styles”, “style library”, “seed from styles” →
references/extract-styles-colors.md - “styles”, “color styles”, “sync Framer colors” →
references/generate-styles.md - “full Framer handoff”, “styles + preview” → styles first (
references/generate-styles.md), then preview (references/generate-preview.md) - “preview”, “swatch board”, “canvas rendering”, “visual board” →
references/generate-preview.md - “semantic tokens”, “color system styles”, “system color styles”,
SystemDatapresent in context →references/generate-styles.md— new semantic style set fromSystemData
When routing a SystemData-based workflow to references/generate-styles.md, pass SystemData opaquely. The sub-skill maps it as follows:
- First: ensure the palette's primitive color styles exist — create them if missing (mandatory prerequisite)
- Create one color style per token, named by the system name + token path (
/systemName/tokenPath) - The
lightvalue is resolved from the first theme ref;darkfrom the second (falls back tolightif absent) - Excluded tokens (
isExcluded: true) and unbound first-theme refs (shadeId: null) are skipped
Note: Framer color styles support only light and dark values — not arbitrary theme modes. Systems with more than 2 themes will use only the first two; the user will be warned.
Platform API references
An agent should think in terms of the Framer Plugin API surface, not only the plugin wrapper:
- Color styles API
- get color styles
- create color style
- set style attributes
- remove color style
- Canvas / node API
- frames and child nodes
- set parent, set attributes, selection
- create/update visual preview documents
- Permissions API
- permission checks before create, update, or remove operations
MCP usage strategy
Use MCP or direct API calls as the execution layer, not as the skill structure.
- The root skill chooses the workflow.
- The reference file defines the expected inputs, transformations, and outputs.
- MCP/API calls execute the chosen workflow.
Agent rule
The plugin bridge files are reference implementations. If the plugin action is unavailable, the agent should reproduce the same behavior directly through Framer API requests.
Recommended subagent
Delegate this skill to palette-transitioner.
The palette-transitioner agent normalizes PaletteData into the correct row model for Framer (styleRows, previewRows), then routes execution through the appropriate Framer sub-skill.
In this repository52 other files it gives its agents.
- gh-cliSkill
- glab-aliasSkill
- glab-apiSkill
- glab-attestationSkill
- glab-authSkill
- glab-changelogSkill
- glab-check-updateSkill
- glab-ciSkill
- glab-clusterSkill
- glab-completionSkill
- glab-configSkill
- glab-deploy-keySkill
- glab-duoSkill
- glab-gpg-keySkill
- glab-helpSkill
- glab-incidentSkill
- glab-issueSkill
- glab-iterationSkill
- glab-jobSkill
- glab-labelSkill
- glab-mcpSkill
- glab-milestoneSkill
- glab-mrSkill
- glab-opentofuSkill
- glab-quick-actionsSkill
- glab-releaseSkill
- glab-repoSkill
- glab-runner-controllerSkill
- glab-runnerSkill
- glab-scheduleSkill
- glab-securefileSkill
- glab-snippetSkill
- glab-ssh-keySkill
- glab-stackSkill
- glab-todoSkill
- glab-tokenSkill
- glab-userSkill
- glab-variableSkill
- glab-versionSkill
- glab-workitemsSkill
- gitlab-cli-skillsSkill
- ui-color-palette-audit-paletteSkill
- ui-color-palette-build-color-systemSkill
- ui-color-palette-figmaSkill
- ui-color-palette-generate-codeSkill
- ui-color-palette-generate-semantic-codeSkill
- ui-color-palette-generate-source-colorsSkill
- ui-color-palette-helpSkill
- ui-color-palette-manage-palettesSkill
- ui-color-palette-penpotSkill
- ui-color-palette-scale-paletteSkill
- ui-color-palette-sketchSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

