From ui-color-palette
Entry point for UI Color Palette workflows targeting Figma. Use to choose between variables and styles generation.
npx claudepluginhub a-ng-d/claude-ui-color-paletteThis skill uses the workspace's default tool permissions.
Use this folder as the platform entry point for all **UI Color Palette → Figma** workflows.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
Use this folder as the platform entry point for all UI Color Palette → Figma workflows.
Figma does not have a native token format. The canonical artifacts in Figma are:
For design token formats (DTCG, Style Dictionary, etc.), use ui-color-palette-generate-code instead.
SKILL.md at the root is the platform indexreferences/ contains the detailed operational sub-skillsBefore calling any MCP tool, check whether PaletteData is already present in the conversation context.
If it is, use it directly — never call get_full_palette again. Confirm to the user:
Using the palette already built in this session. Generating Figma artifacts now.
Only rebuild the palette if the user explicitly asks to change colors, preset, or themes.
This platform skill is primarily a routing and orchestration layer.
The agent should:
references/Do not start from raw API calls. Start from the workflow structure.
references/generate-variables.md — generate or sync Figma local variables and modesreferences/generate-styles.md — generate or sync Figma local paint stylesreferences/generate-tokens.md — orchestrate variables, styles, and document preview togetherChoose the sub-skill by user intent:
references/generate-variables.mdreferences/generate-styles.mdreferences/generate-tokens.mdIf the user asks for "tokens" in the context of Figma, clarify that Figma does not have a native token format and route to variables instead. If they want exportable design tokens, route to ui-color-palette-generate-code.
An agent should think in terms of the Figma Plugin API surface, not only the plugin wrapper:
Use MCP or direct API calls as the execution layer, not as the skill structure.
The plugin bridge files are reference implementations. If the plugin action is unavailable, the agent should reproduce the same behavior directly through Figma API requests.
Delegate this skill to palette-transitioner.
The palette-transitioner agent normalizes PaletteData into the correct row model for Figma (variableRows, styleRows, previewRows), then routes execution through the appropriate Figma sub-skill.