ui4

A manually started workflow for changing the appearance of Payload UI components to match a Figma design, a shared interface-design file.

In plain words
What is it for?
Use it to reskin Payload UI components from a Figma URL, check icon imports, compare available icons, and flag icons that must be added.
Why use it?
It helps identify icon differences between the design and the existing code before changing a component.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/payloadcms/payload/ui4
Any agent
npx skills add payloadcms/payload --skill ui4
Clone the repo
git clone --depth 1 https://github.com/payloadcms/payload

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,035 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.06035
Opus 5 $0.00013 $0.03018
Sonnet 5 $0.00005 $0.01207
Haiku 4.5 $0.00003 $0.00604

Measured yesterday against content hash 827f5ac0acd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ui4 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/ui4/SKILL.md · 646 lines

How it starts

The opening of the file, as written. The whole thing — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Payload UI Reskin (ui4)

Figma URL is REQUIRED. If not provided, ask before proceeding.


Process

Step 0: Icon Scan

Goal: Identify icon dependencies before starting work.

  1. Scan component files for icon imports:

    grep -E "from.*icons|import.*Icon" packages/ui/src/elements/ComponentName/
    
  2. List existing icons in packages/ui/src/icons/:

    • Each icon has its own folder with index.tsx + index.css
  3. Compare Figma design to available icons:

    • Does the design use icons not currently in the component?
    • Does the design use icons that don't exist yet?
  4. Document findings:

    • Existing & used: No action needed
    • Existing but not imported: Will need to add import
    • Missing from codebase: Flag for user — need to source/create icon

Figma Icons Source:

When updating or creating icons, reference the Figma icon library at:

~/figma/figma/fpl/icons/src/icons/

Icon naming convention: icon-{size}-{name}.tsx (e.g., icon-16-close.tsx, icon-24-chevron-down.tsx)

To find the correct icon:

  1. Note the icon name from Figma design (e.g., "close", "chevron-down")
  2. Check both 16px and 24px variants if they exist
  3. Read the corresponding files and extract the SVG paths for each size

Icon implementation rules:

  1. Props: Icon components MUST accept these props (keep existing props when updating):

    type IconProps = {
      readonly className?: string
      readonly size?: 16 | 24 // Add more sizes as needed
      // ... keep any existing component-specific props
    }
    
  2. Multi-size support: Store path data keyed by size:

    const paths = {
      16: 'M4.854 4.146...', // from icon-16-{name}.tsx
      24: 'M6.854 6.146...', // from icon-24-{name}.tsx
    }
    
  3. SVG rendering: Use the size prop to select path and viewBox:

    <svg width={size} height={size} viewBox={`0 0 ${size} ${size}`} fill="none">
      <path d={paths[size]} fill="currentColor" />
    </svg>
    

Read the full file on GitHub · 646 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 646 lines · 0 tokens per session scan A 827f5ac0acd4

Subscribe to this mod's changes

ui4 is a skill published in the GitHub repository payloadcms/payload (44,499 stars, last pushed 3d ago), licensed MIT. It adds 25 tokens to every session and 6,035 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

webiny-api-cms-content-models

Creating Headless CMS content models via code using the ModelFactory pattern. Use this skill when the developer wants to create, modify, or understand content model definitions, define fields and validators, set up reference fields between models, configure field layouts (including nested layouts inside object or…

webiny/webiny-js · 297 tokens

webiny-form-model

Building forms with the FormModel system — field types, renderers, layout, validation, conditional rules, computed fields, and dynamic zones. Use this skill when the developer needs to define form fields with the builder API, choose renderers, build layouts with tabs/rows/separators, add validation (Zod or…

webiny/webiny-js · 93 tokens

webiny-api-architect

The hub skill for all API/backend architecture in Webiny. Covers architecture overview, Services vs UseCases, feature naming and organization, feature structure templates, DI decision tree, anti-patterns, createFeature, createAbstraction, container registration, domain errors, entity patterns, naming conventions…

webiny/webiny-js · 90 tokens

webiny-v5-to-v6-migration

Migration patterns for converting v5 Webiny code to v6 architecture. Use this skill when migrating existing v5 plugins to v6 features, converting context plugins to DI services, adapting v5 event subscriptions to v6 EventHandlers, or understanding how v5 patterns translate to v6. Targeted at AI agents performing…

webiny/webiny-js · 75 tokens

webiny-admin-architect

Admin-side architecture patterns for Webiny extensions. Use this skill when building frontend features with headless features (UseCase/Repository/Gateway), presentation features (Presenter/ViewModel/hooks/components), MobX-based presenters, RegisterFeature, and Admin BuildParams. Covers the admin/ directory structure…

webiny/webiny-js · 71 tokens

webiny-cognito-federation

Configuring Cognito Federation for Webiny projects — federated sign-in via external identity providers (Google, Facebook, Apple, Amazon, OIDC/Entra ID) while keeping Cognito as the user pool. Use this skill when the developer asks about Cognito federation, SSO with Cognito, adding Google/Microsoft/OIDC login to…

webiny/webiny-js · 126 tokens