Skill

ui-color-palette-penpot

Entry point for UI Color Palette workflows targeting Penpot. Use to choose between tokens, styles, and board/document preview generation.

Install

npx claudepluginhub a-ng-d/claude-ui-color-palette

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use this folder as the platform entry point for all **UI Color Palette → Penpot** workflows.

Supporting Assets

references/generate-styles.mdreferences/generate-tokens.md

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

mcp-builder

9 files

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

anthropics-skills-13

124.2k

canvas-design

20 files

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

anthropics-skills-13

124.2k

Stats

Stars0

Forks0

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

UI Color Palette Penpot

Use this folder as the platform entry point for all UI Color Palette → Penpot workflows.

Folder structure

SKILL.md at the root is the platform index
references/ 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_full_palette again. Confirm to the user:

Using the palette already built in this session. Generating Penpot 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 tokens, 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/generate-tokens.md — generate or sync Penpot local tokens and themed sets
references/generate-styles.md — generate or sync Penpot local color styles

Routing

Choose the sub-skill by user intent:

“tokens”, “semantic colors”, “theme tokens”, “Penpot token sets” → references/generate-tokens.md
“styles”, “local colors”, “style library”, “swatches” → references/generate-styles.md
“preview”, “board”, “document review” → usually start with references/generate-tokens.md, then generate/update the document preview

Platform API references

An agent should think in terms of the Penpot plugin/API surface, not only the plugin wrapper:

Local token catalog API
- token sets
- tokens
- themes and theme groups
Local style/color API
- local library colors
- style path, name, color, opacity
Document API
- boards/documents
- node creation and update
- plugin data on current page/document

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 Penpot API requests.

Recommended subagent

Delegate this skill to palette-transitioner.

The palette-transitioner agent normalizes PaletteData into the correct row model for Penpot (tokenRows, styleRows, previewRows), then routes execution through the appropriate Penpot sub-skill.