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…
Helps create and modify UUI (EPAM Unified UI) components following established patterns.
$ npx skills add epam/UUI --skill uui-components -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install epam/UUI uui-components --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "uui-components" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/components into .claude/skills/uui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-components", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/epam/UUI/tree/develop/.cursor/skills/componentsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add epam/UUI --skill uui-components -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install epam/UUI uui-components --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/components .agents/skills/uui-components && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "uui-components" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/components into .agents/skills/uui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-components", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add epam/UUI --skill uui-components -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install epam/UUI uui-components --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/components .cursor/skills/uui-components && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "uui-components" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/components into .cursor/skills/uui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-components", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/epam/UUI.git --path .cursor/skills/components--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add epam/UUI --skill uui-components -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install epam/UUI uui-components --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/components .gemini/skills/uui-components && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "uui-components" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/components into .gemini/skills/uui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-components", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install epam/UUI uui-componentsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add epam/UUI --skill uui-components -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/components .github/skills/uui-components && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "uui-components" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/components into .github/skills/uui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-components", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add epam/UUI --skill uui-components -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install epam/UUI uui-components --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/components .opencode/skills/uui-components && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "uui-components" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/components into .opencode/skills/uui-components/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-components", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
uui-componentsHelps 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. 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.
3 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fd11393. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from epam/UUI at commit fd11393, republished under its MIT licence (© epam). 543 words, ~2,808 tokens.
.claude/skills/uui-components/SKILL.md (or your agent's skills folder).@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/.
Components are organized by category in uui/components/:
| Category | Path | Examples |
|---|---|---|
| buttons | uui/components/buttons/ | Button, IconButton, LinkButton |
| inputs | uui/components/inputs/ | Checkbox, TextInput, NumericInput, Switch |
| typography | uui/components/typography/ | Text, TextPlaceholder, RichTextView |
| overlays | uui/components/overlays/ | Modal, Tooltip, DropdownMenu |
| layout | uui/components/layout/ | FlexRow, FlexCell, Blocker |
| pickers | uui/components/pickers/ | PickerInput, PickerModal |
| datePickers | uui/components/datePickers/ | DatePicker, RangeDatePicker |
| dnd | uui/components/dnd/ | Drag and drop |
| widgets | uui/components/widgets/ | Tag, Badge, Spinner |
| tables | uui/components/tables/ | DataTable |
| filters | uui/components/filters/ | FiltersPanel |
| navigation | uui/components/navigation/ | MainMenu, TabButton |
| forms | uui/components/forms/ | Form components |
| fileUpload | uui/components/fileUpload/ | File upload |
| errors | uui/components/errors/ | Error handling |
Each component typically has:
ComponentName.tsx — Component implementationComponentName.module.scss — Styles (SCSS modules)__tests__/ComponentName.test.tsx — Unit testsuui-components ComponentWhen wrapping a logic-only component from @epam/uui-components:
Example: IconButton
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 stringsOverwrite<Mods, ModsOverride> pattern for extensibilityuui-components Counterpart)When creating a component from scratch:
Example: TextPlaceholder
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:
withMods if not themeableIHasCX and IHasRawProps from @epam/uui-core for standard propscx (classnames) for conditional classesComponents use SCSS modules (.module.scss):
// IconButton.module.scss
.root {
display: inline-flex;
align-items: center;
// Styles here
}Import in component:
import css from './IconButton.module.scss';The applyMods function maps props to CSS classes:
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:
css.root for component-specific stylesuui-* prefixed classes for themeable utilitiessettings.componentName.* for default valueswithMods)Each category folder has an index.ts that re-exports components:
// uui/components/buttons/index.ts
export * from './Button';
export * from './IconButton';
export * from './LinkButton';Main uui/components/index.ts re-exports all categories:
// uui/components/index.ts
export * from './buttons';
export * from './inputs';
export * from './typography';
// ... etcWhen adding a new component:
export const MyComponent = ...index.ts: export * from './MyComponent';index.ts: export * from './newCategory';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:
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} />The settings object (uui/settings.tsx) provides theme-specific defaults: icons, sizes, placeholders. Structure: settings.<component>.<category>.<key>.
Access:
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).
The third parameter of withMods can transform props:
export const TextInput = withMods<CoreTextInputProps, TextInputProps>(
uuiTextInput,
applyTextInputMods,
() => ({
acceptIcon: settings.textInput.icons.acceptIcon,
cancelIcon: settings.textInput.icons.clearIcon,
dropdownIcon: settings.textInput.icons.dropdownIcon,
}),
);Apply mods conditionally in applyMods:
function applyCheckboxMods(mods: CheckboxMods) {
return [
css.root,
`uui-size-${mods.size || settings.checkbox.sizes.default}`,
'uui-control-mode-' + (mods.mode || 'form'),
'uui-color-primary',
];
}forwardRefMany components expose refs via React.forwardRef. Use when consumers need direct DOM access (e.g. focus management, measurements):
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:
export const Tag = React.forwardRef<HTMLElement, TagProps>((props, ref) => {
return (
<div ref={ ref } className={ cx(applyTagMods(props), props.cx) }>
{/* ... */}
</div>
);
});withMods)Some components apply mods manually instead of using withMods. This is common when wrapping primitives like Clickable with forwardRef:
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.
Components like DataTable, PickerInput, PickerModal, and FiltersPanel use DataSource from @epam/uui-core. See .cursor/skills/data-sources/SKILL.md for DataSource usage.
Use devLogger to warn about deprecated prop values:
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.",
});uui/components/buttons/IconButton.tsxuui/components/typography/TextPlaceholder.tsxuui/components/inputs/TextInput.tsxuui/components/buttons/Button.tsxuui/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
Just SKILL.md in .cursor/skills/components of epam/UUI.
Open the folder on GitHubat commit fd11393
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Uui Components this skillepam/UUI | 248 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Impeccablebestofjs/bestofjs | 3.1k | 27 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Shadcnsupabase/evals | 143 | 42 repos | ~4.5k | Automated safety check: Pass | Apache-2.0 |
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…
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
warpdotdev/warp
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.
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.
supabase/evals
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI.
Ohh-889/skyroc
Token architecture, component specifications, and slide generation.
epam/UUI
Helps work with UUI DataSources (ArrayDataSource, LazyDataSource, AsyncDataSource) powering PickerInput, DataTable, FiltersPanel, and other data-driven components.
epam/UUI
Helps update UUI documentation, add doc examples, configure Property Explorer, and manage component API documentation.
epam/UUI
Helps create and maintain E2E and screenshot tests for UUI components using Playwright.
epam/UUI
Fetches GitHub issues from URLs and creates implementation plans for UUI.
epam/UUI
Guides the UUI pull request process including branch naming, pre-PR checklist, changelog updates, and quality requirements.
epam/UUI
Helps work with UUI services layer including ContextProvider, ApiContext, ModalContext, NotificationContext, and useUuiContext.
Categories
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.
Uui Components fits situations like: creating new components; modifying existing components; working with withMods; component props.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Uui Components is instructions for the agent only.
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.
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.
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.
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.
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.
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.