Agent skill

Uui Components

by epam in epam/UUI

Helps create and modify UUI (EPAM Unified UI) components following established patterns.

MITAuto-check passedFrontend & Design

Install Uui Components

skills CLI
$ npx skills add epam/UUI --skill uui-components -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install epam/UUI uui-components --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/components .claude/skills/uui-components && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
uui-components
GitHub stars
248
Token cost
~2.8k tokens
SKILL.md length
543 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Helps create and modify UUI (EPAM Unified UI) components following established patterns.

  • Works in 3 steps: Export from component file: export const… → Add to category index.ts: export * from… → If new category, add to root index.ts:…
  • Creating new components
  • SKILL.md covers Package Structure, File Path Conventions, Component Creation Workflows and Styling Patterns, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Uui Components is an agent skill from epam/UUI. Helps create and modify UUI (EPAM Unified UI) components following established patterns. Use when creating new components, modifying existing components, working with withMods, component props, styling, or component architecture in the UUI library.

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design systems. The repository describes itself as: React-based components and accelerators library built by EPAM Systems. The licence is MIT.

When your agent uses it

  • Creating new components
  • Modifying existing components
  • Working with withMods
  • Component props

Example prompts

  • “Use the uui-components skill to help create and modify UUI (EPAM Unified UI) components following established patterns”
  • “/uui-components”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Export from component file: export const MyComponent = ...
  2. Add to category index.ts: export * from './MyComponent';
  3. If new category, add to root index.ts: export * from './newCategory';

What it can do on your machine

Read from SKILL.md and the folder at commit fd11393. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and scss).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Uui Components loads about 2.8k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 543 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from epam/UUI at commit fd11393, republished under its MIT licence (© epam). 543 words, ~2,808 tokens.

Download SKILL.mdSave it as .claude/skills/uui-components/SKILL.md (or your agent's skills folder).
name
uui-components
description
Helps create and modify UUI (EPAM Unified UI) components following established patterns. Use when creating new components, modifying existing components, working with withMods, component props, styling, or component architecture in the UUI library.

UUI Components Skill

Package Structure

  • @epam/uui-components — Legacy package with logic-only components (no visual styles). Contains older components.
  • @epam/uui — Package for ready-to-use, themeable components. All new components must be created here in the uui/ folder.

When creating new components, add them to uui/components/, not to uui-components/.

File Path Conventions

Components are organized by category in uui/components/:

CategoryPathExamples
buttonsuui/components/buttons/Button, IconButton, LinkButton
inputsuui/components/inputs/Checkbox, TextInput, NumericInput, Switch
typographyuui/components/typography/Text, TextPlaceholder, RichTextView
overlaysuui/components/overlays/Modal, Tooltip, DropdownMenu
layoutuui/components/layout/FlexRow, FlexCell, Blocker
pickersuui/components/pickers/PickerInput, PickerModal
datePickersuui/components/datePickers/DatePicker, RangeDatePicker
dnduui/components/dnd/Drag and drop
widgetsuui/components/widgets/Tag, Badge, Spinner
tablesuui/components/tables/DataTable
filtersuui/components/filters/FiltersPanel
navigationuui/components/navigation/MainMenu, TabButton
formsuui/components/forms/Form components
fileUploaduui/components/fileUpload/File upload
errorsuui/components/errors/Error handling

Each component typically has:

  • ComponentName.tsx — Component implementation
  • ComponentName.module.scss — Styles (SCSS modules)
  • __tests__/ComponentName.test.tsx — Unit tests

Component Creation Workflows

Workflow 1: Wrapping Existing uui-components Component

When wrapping a logic-only component from @epam/uui-components:

Example: IconButton

typescript
import * as uuiComponents from '@epam/uui-components';
import { withMods, Overwrite } from '@epam/uui-core';
import { settings } from '../../settings';
import css from './IconButton.module.scss';

// 1. Define mods type for themeable properties
interface IconButtonMods {
    color?: 'info' | 'success' | 'error' | 'primary' | 'accent' | 'critical' | 'warning' | 'secondary' | 'neutral' | 'white';
    size?: '18' | '24' | '30' | '36';
}

export interface IconButtonModsOverride {}

// 2. Create props interface extending core props
export type IconButtonCoreProps = Omit<uuiComponents.IconButtonProps, 'size'>;
export interface IconButtonProps extends IconButtonCoreProps, Overwrite<IconButtonMods, IconButtonModsOverride> {}

// 3. Create applyMods function that returns CSS classes
function applyIconButtonMods(props: IconButtonProps) {
    return [
        'uui-icon_button',
        `uui-color-${props.color || 'neutral'}`,
        css.root, // SCSS module class
    ];
}

// 4. Wrap with withMods HOC
export const IconButton = withMods<uuiComponents.IconButtonProps, IconButtonProps>(
    uuiComponents.IconButton, // Core component
    applyIconButtonMods, // Mods function
    (props) => {
        // Optional: transform props or add defaults
        return {
            dropdownIcon: props.dropdownIcon || settings.iconButton.icons.dropdownIcon,
        };
    },
);

Key points:

  • withMods<CoreProps, Props>(coreComponent, applyMods, propsTransformer?)
  • applyMods returns array of CSS class strings
  • Third parameter is optional function to transform/inject props
  • Use Overwrite<Mods, ModsOverride> pattern for extensibility
Workflow 2: Brand-New Component (No uui-components Counterpart)

When creating a component from scratch:

Example: TextPlaceholder

typescript
import * as React from 'react';
import cx from 'classnames';
import { IHasCX, IHasRawProps } from '@epam/uui-core';
import css from './TextPlaceholder.module.scss';
import { PropsWithChildren } from 'react';

// 1. Define props interface
export interface ITextPlaceholderProps extends IHasRawProps<React.HTMLAttributes<HTMLDivElement>>, IHasCX {
    wordsCount?: number;
    isNotAnimated?: boolean;
}

export type TextPlaceholderProps = PropsWithChildren<ITextPlaceholderProps>;

// 2. Implement component directly
export const TextPlaceholder: React.FunctionComponent<TextPlaceholderProps> = (props) => {
    // Component logic here
    return (
        <div className={cx(css.root, 'uui-text-placeholder')} {...props.rawProps}>
            {/* Component JSX */}
        </div>
    );
};

Key points:

  • Implement directly without withMods if not themeable
  • Use IHasCX and IHasRawProps from @epam/uui-core for standard props
  • Use cx (classnames) for conditional classes
  • Use SCSS modules for styling

Styling Patterns

SCSS Modules

Components use SCSS modules (.module.scss):

scss
// IconButton.module.scss
.root {
    display: inline-flex;
    align-items: center;
    // Styles here
}

Import in component:

typescript
import css from './IconButton.module.scss';
Mods to CSS Classes

The applyMods function maps props to CSS classes:

typescript
function applyButtonMods(mods: ButtonProps) {
    return [
        css.root, // SCSS module class
        'uui-button', // Global UUI class
        `uui-fill-${mods.fill || 'solid'}`, // Dynamic class from prop
        `uui-color-${mods.color || 'primary'}`,
        `uui-size-${mods.size || settings.button.sizes.default}`,
    ];
}

Patterns:

  • Use css.root for component-specific styles
  • Use uui-* prefixed classes for themeable utilities
  • Use settings.componentName.* for default values
  • Return array of class strings (will be joined by withMods)

Export Pattern

Component-Level Index

Each category folder has an index.ts that re-exports components:

typescript
// uui/components/buttons/index.ts
export * from './Button';
export * from './IconButton';
export * from './LinkButton';
Root Index

Main uui/components/index.ts re-exports all categories:

typescript
// uui/components/index.ts
export * from './buttons';
export * from './inputs';
export * from './typography';
// ... etc

When adding a new component:

  1. Export from component file: export const MyComponent = ...
  2. Add to category index.ts: export * from './MyComponent';
  3. If new category, add to root index.ts: export * from './newCategory';
Show full SKILL.md (212 more words)Show less

Common Patterns

cx Prop (IHasCX)

Most components extend IHasCX, which adds a cx prop for consumer styling. Always merge props.cx into the root element's classNames so consumers can pass custom classes:

typescript
import cx from 'classnames';

// With withMods — withMods merges cx automatically
// Manual mods:
<div className={cx(applyTagMods(props), props.cx)}>
<Clickable cx={cx(applyTagMods(props), props.cx)} {...props} />
Using Settings

The settings object (uui/settings.tsx) provides theme-specific defaults: icons, sizes, placeholders. Structure: settings.<component>.<category>.<key>.

Access:

typescript
import { settings } from '../../settings';

// Icons
dropdownIcon: props.dropdownIcon || settings.iconButton.icons.dropdownIcon,
// Sizes
size: props.size || settings.button.sizes.default,

Structure: Each component has nested objects (e.g. icons, sizes). Themes override via PartialSettings — see skin packages (loveship, epam-electric, epam-promo) for how settings are merged. To add new component settings, add a section in uui/settings.tsx following existing patterns (e.g. accordionSettings, buttonSettings).

Props Transformation

The third parameter of withMods can transform props:

typescript
export const TextInput = withMods<CoreTextInputProps, TextInputProps>(
    uuiTextInput,
    applyTextInputMods,
    () => ({
        acceptIcon: settings.textInput.icons.acceptIcon,
        cancelIcon: settings.textInput.icons.clearIcon,
        dropdownIcon: settings.textInput.icons.dropdownIcon,
    }),
);
Conditional Mods

Apply mods conditionally in applyMods:

typescript
function applyCheckboxMods(mods: CheckboxMods) {
    return [
        css.root,
        `uui-size-${mods.size || settings.checkbox.sizes.default}`,
        'uui-control-mode-' + (mods.mode || 'form'),
        'uui-color-primary',
    ];
}

Additional Patterns

Using forwardRef

Many components expose refs via React.forwardRef. Use when consumers need direct DOM access (e.g. focus management, measurements):

typescript
import React from 'react';
import { withMods } from '@epam/uui-core';
import * as uuiComponents from '@epam/uui-components';

// withMods works with forwardRef components automatically.
// If the core component uses forwardRef, the wrapped component inherits it.
export const Switch = withMods<uuiComponents.SwitchProps, SwitchProps>(uuiComponents.Switch, applySwitchMods);

For brand-new components without withMods:

typescript
export const Tag = React.forwardRef<HTMLElement, TagProps>((props, ref) => {
    return (
        <div ref={ ref } className={ cx(applyTagMods(props), props.cx) }>
            {/* ... */}
        </div>
    );
});
Manual Mods (without withMods)

Some components apply mods manually instead of using withMods. This is common when wrapping primitives like Clickable with forwardRef:

typescript
export const Tag = React.forwardRef<HTMLElement, TagProps>((props, ref) => {
    return (
        <Clickable
            cx={ cx(applyTagMods(props), props.cx) }
            ref={ ref }
            { ...props }
        />
    );
});

function applyTagMods(props: TagProps) {
    return [
        css.root,
        `uui-size-${props.size || '36'}`,
        `uui-color-${props.color || 'neutral'}`,
    ];
}

See uui/components/widgets/Tag.tsx, uui/components/layout/FlexRow.tsx for examples.

Data-Driven Components (DataTable, PickerInput)

Components like DataTable, PickerInput, PickerModal, and FiltersPanel use DataSource from @epam/uui-core. See .cursor/skills/data-sources/SKILL.md for DataSource usage.

Deprecation Warnings

Use devLogger to warn about deprecated prop values:

typescript
import { devLogger } from '@epam/uui-core';

devLogger.warnAboutDeprecatedPropValue<IconButtonProps, 'color'>({
    component: 'IconButton',
    propName: 'color',
    propValue: props.color,
    condition: () => ['info', 'success'].includes(props.color),
    message: "'info' and 'success' colors are deprecated. Use 'primary' instead.",
});

References

  • Example wrapping component: uui/components/buttons/IconButton.tsx
  • Example brand-new component: uui/components/typography/TextPlaceholder.tsx
  • Example with complex mods: uui/components/inputs/TextInput.tsx
  • Example with props transformation: uui/components/buttons/Button.tsx
  • Example with forwardRef + manual mods: uui/components/widgets/Tag.tsx

© epam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .cursor/skills/components of epam/UUI.

Open the folder on GitHubat commit fd11393

Compare with similar skills

Uui Components next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Uui Components compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Uui Components this skillepam/UUI248—~2.8kAutomated safety check: PassMIT
Impeccablebestofjs/bestofjs3.1k27 repos~2.6kAutomated safety check: PassMIT
Figma Design System Builderwarpdotdev/warp65k2 repos~4.4kAutomated safety check: PassAGPL-3.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
UI StylingOhh-889/skyroc79513 repos~2.5kAutomated safety check: PassMIT
Shadcnsupabase/evals14342 repos~4.5kAutomated safety check: PassApache-2.0

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 27 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.

    65k GitHub starsUsed in 2 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed
  • UI Styling

    Ohh-889/skyroc

    Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.

    795 GitHub starsUsed in 13 repos~2.5k tokens
    Frontend & DesignAuto-check passed
  • Shadcn

    supabase/evals

    Official

    Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI.

    143 GitHub starsUsed in 42 repos~4.5k tokens
    Frontend & DesignAuto-check passed
  • Design System

    Ohh-889/skyroc

    Token architecture, component specifications, and slide generation.

    795 GitHub starsUsed in 11 repos~1.7k tokens
    Frontend & DesignAuto-check passed

More from epam/UUI

All 10 skills in this repo
  • Helps work with UUI DataSources (ArrayDataSource, LazyDataSource, AsyncDataSource) powering PickerInput, DataTable, FiltersPanel, and other data-driven components.

    248 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed
  • Helps update UUI documentation, add doc examples, configure Property Explorer, and manage component API documentation.

    248 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Helps create and maintain E2E and screenshot tests for UUI components using Playwright.

    248 GitHub stars~1.3k tokensUpdated 8 days ago
    Auto-check passed
  • Fetches GitHub issues from URLs and creates implementation plans for UUI.

    248 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check passed
  • Guides the UUI pull request process including branch naming, pre-PR checklist, changelog updates, and quality requirements.

    248 GitHub stars~1.7k tokensUpdated 8 days ago
    Auto-check: notes
  • Helps work with UUI services layer including ContextProvider, ApiContext, ModalContext, NotificationContext, and useUuiContext.

    248 GitHub stars~1.2k tokensUpdated 8 days ago
    Auto-check passed

Questions about Uui Components

What does Uui Components do?

Helps create and modify UUI (EPAM Unified UI) components following established patterns. Uui Components is an agent skill from epam/UUI. Helps create and modify UUI (EPAM Unified UI) components following established patterns.

When should I use Uui Components?

Uui Components fits situations like: creating new components; modifying existing components; working with withMods; component props.

How do I install Uui Components in Claude Code?

Run `npx skills add epam/UUI --skill uui-components -a claude-code`. Or copy the skill folder (.cursor/skills/components in epam/UUI) into .claude/skills/uui-components in your project. Claude Code loads it when a task matches its description.

How do I install Uui Components in Codex?

Run `npx skills add epam/UUI --skill uui-components -a codex`. Or copy the skill folder (.cursor/skills/components in epam/UUI) into .agents/skills/uui-components in your project. Codex loads it when a task matches its description.

Can I use Uui Components in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/UUI --skill uui-components -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uui-components, .gemini/skills/uui-components, .github/skills/uui-components and .opencode/skills/uui-components in your project.

What does Uui Components need to run?

SKILL.md names no scripts, command-line tools or credentials: Uui Components is instructions for the agent only.

Does Uui Components access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Uui Components safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Uui Components use?

Uui Components is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Uui Components use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Uui Components?

Skills that share tags, products or a category with Uui Components: Impeccable (bestofjs/bestofjs, 3.1k stars), Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars) and UI Styling (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Uui Components?

epam (a GitHub organization) maintains it in epam/UUI, which has 248 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 29, 2026.

Source: epam/UUI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.