<< All versions
Skill v1.0.0
currentAutomated scanlightspeedwp/.github/figma-themejson-palette
──Details
PublishedOctober 6, 2026 at 02:05 AM
Content Hashsha256:f37ad555a5d7ee1d...
Git SHA
──Files
Files (1 file, 1.9 KB)
SKILL.md1.9 KBactive
SKILL.md · 59 lines · 1.9 KB
name: figma-themejson-palette description: Extract a WordPress theme.json color palette from a Figma variables table. Use when the user provides a Figma node URL or ID for palette variables and needs palette-ready settings.color.palette entries with stable slugs, names, and hex values. metadata: version: "1.0.0"
Figma ThemeJSON Palette
Overview
Extract a WordPress theme.json palette from a Figma variables table.
Use this skill when the input is a Figma node containing color variables that should become settings.color.palette entries.
Required Input
- Figma node URL or node ID for the palette variables table
If the node is missing, ask for it before continuing.
Workflow
- Read the Figma variables from the provided node.
- Identify palette candidates only. Exclude semantic usage tokens that belong in
settings.custom.color. - Normalize each palette entry into:
nameslugcolor
- Prefer broad family scales such as
neutral-100,brand-500, oraccent-700when the Figma naming supports them. - Preserve coherent existing naming systems instead of forcing a new one.
- Convert colors to normalized hex values.
- Flag duplicate colors, naming collisions, missing scale steps, and ambiguous palette families.
- Output only palette-ready entries plus concise notes.
Output Contract
Return:
Palette Entries
- one bullet or code block entry per palette token with
name,slug, andcolor
Notes
- ambiguous mappings
- duplicate or conflicting palette entries
- naming cleanup recommendations
Guardrails
- Do not invent semantic custom color tokens here.
- Do not emit raw Figma metadata unless it helps explain a mapping issue.
- Do not guess missing colors.
- Keep output focused on
settings.color.palette.
_Built by 🧱 LightSpeedWP with ☕, 🚀, and open-source spirit!_ Contributors