← ClaudeAtlas

figma-color-palettelisted

Generate a complete, Tailwind-compatible Figma color palette (variables + a reusable "Color Tag" badge component + a documented "Color Section" frame, assembled into a page-level "Documentation" frame with Header/Footer and a wrapping 3-column grid) from a base hex or a full list of colors. Works even in a brand-new file with no existing "Color Tag" component — the skill creates it from scratch on first use. Use this skill whenever the user asks to create, generate, or add a color palette in Figma, wants Figma color variables for a design system, mentions "primitives-{name}", "Color Tag", "gap-6", "Color Section", "Documentation", or "grid" in a Figma color-system context, or wants a reusable Figma skill for generating color scales (050-950). Always trigger this before writing any Figma Plugin API code for palette generation — it defines the mandatory intake questions, the HSL scale algorithm, the exact variable/component/frame specs, and a validation script, so nothing has to be invented or guessed.
theotible-pro/figma-color-palette · ★ 2 · Web & Frontend · score 70
Install: claude install-skill theotible-pro/figma-color-palette
# Figma Color Palette Generator Generates a complete, reusable color palette inside any Figma file — for any designer, not just one project. Produces: Figma variables (color + string placeholders), a reusable `Color Tag` component (created from scratch if the file doesn't already have one), and a documented `Color Section` frame — all wired together with bound variables so a designer can rename/recolor later without touching instances. Each `Color Section` is assembled into a page-level `Documentation` frame (Header + wrapping 3-column `grid` + Footer), so multiple palettes accumulate into one consistent page instead of scattering loose sections. **Always writes through `use_figma`** (Figma Plugin API), following the `figma-use` skill's rules: work incrementally, validate after each step, return all created/mutated node IDs, never guess font style names, always set explicit variable scopes. Before writing any creation code, skim `references/figma-api-patterns.md` once per session — it has the exact, tested API call shapes (page persistence, variable binding, auto-layout sizing) that are easy to get subtly wrong from memory. Reaching for that file when unsure is expected, not optional overhead. --- > ## 🔒 Non-negotiables (read before anything else) > These are things past runs of this skill have actually skipped or > gotten wrong. If a generation doesn't tick every one of these, it > isn't done — no exceptions, no "I'll add it after": > 1. **Every `Color Section` lives in