New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Update Component Styles

by IgniteUI in IgniteUI/igniteui-webcomponents

Update component styling following the SCSS to Lit CSS workflow with proper theme support

MITAuto-check passedFrontend & Design

Install Update Component Styles

skills CLI
$ npx skills add IgniteUI/igniteui-webcomponents --skill update-component-styles -a claude-code

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

GitHub CLI
$ gh skill install IgniteUI/igniteui-webcomponents update-component-styles --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/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-component-styles .claude/skills/update-component-styles && 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
update-component-styles
GitHub stars
170
Token cost
~1.3k tokens
SKILL.md length
462 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Update component styling following the SCSS to Lit CSS workflow with proper theme support

  • Works in 3 steps: Edit the SCSS → Document new parts or custom properties → Transpile and verify
  • Tasks that involve CSS and styling
  • SKILL.md covers Where a Change Goes, Steps, Validation Checklist and Common Pitfalls, plus 1 more section
  • Calls npm

What it does

Update Component Styles is an agent skill from IgniteUI/igniteui-webcomponents. Update component styling following the SCSS to Lit CSS workflow with proper theme support

Its SKILL.md is about 1.3k 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 CSS and styling. The repository describes itself as: Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable… The licence is MIT.

When your agent uses it

  • Tasks that involve CSS and styling

Example prompts

  • “/update-component-styles”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Edit the SCSS
  2. Document new parts or custom properties
  3. Transpile and verify

What it can do on your machine

Read from SKILL.md and the folder at commit ab2cd1d. 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

    Shell commands in SKILL.md call:

    • npm

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

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    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

Update Component Styles loads about 1.3k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 462 words of instructions outside code blocks.

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

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 IgniteUI/igniteui-webcomponents at commit ab2cd1d, republished under its MIT licence (© IgniteUI). 462 words, ~1,284 tokens.

Download SKILL.mdSave it as .claude/skills/update-component-styles/SKILL.md (or your agent's skills folder).
name
update-component-styles
description
Update component styling following the SCSS to Lit CSS workflow with proper theme support

Update Component Styles

Changes component styles through the SCSS → Lit CSS build and the igniteui-theming schemas. The directory layout and rules are in Styles and Theming.

Related: create-new-component for a new theme scaffold.

Where a Change Goes

ChangeFile
Layout, sizing, structure[component].base.scss
Styling that reads theme variablesshared/[component].common.scss
One theme is structurally differentshared/[component].[theme].scss
A color or elevation for one themelight/ or dark/[component].[theme].scss
A new variable for every themelight/[component].shared.scss

Steps

1. Edit the SCSS

Use 4-space indentation and load-path specifiers (@use 'styles/utilities' as *), not relative paths into src/styles. Read theme values with var-get():

scss
// shared/[component].common.scss
@use 'styles/utilities' as *;
@use '../light/themes' as *;

$theme: $material;

[part~='base'] {
    background: var-get($theme, 'background');
    color: var-get($theme, 'text-color');
}
scss
// dark/[component].bootstrap.scss: emit only the difference from the light base
@use 'styles/utilities' as *;
@use 'themes' as *;
@use '../light/themes' as light;

$theme: $bootstrap;

:host {
    @include css-vars-from-theme(diff(light.$base, $theme));
}
  • Do not hardcode colors or sizes. Use var-get(), color(), contrast-color(), sizable() and --ig-size.
  • Match parts with [part~='name']. partMap emits a space-separated list.
  • Keep specificity low. Document the custom properties that consumers can set, and prefix internal ones with --_.
  • Key composite-anchor selectors off data-role / data-haspopup, not role / aria-* (see ARIA across shadow boundaries).
  • var-get() resolves only keys that are in the schema. For a new key, add it to igniteui-theming, or declare a local variable in shared/[component].common.scss.
2. Document new parts or custom properties
ts
/**
 * @csspart base - The main container.
 * @cssproperty --component-padding - The internal padding.
 */

Run npm run cem && npm run build:meta. Parts and custom properties are public API, so also add a row to ### CSS Shadow parts or ### CSS custom properties in spec.md, add a TOC entry for a new section, and add a row to ## Revision history. A visual change that adds no part or property does not change the spec, unless it contradicts documented behavior.

3. Transpile and verify
bash
npm run build:styles
npm run lint:styles
npm run storybook

npm run storybook and npm run test:watch also rebuild the styles when you save. Check all four themes in light and dark mode.

[!IMPORTANT] The generated .css.ts files are gitignored. Do not edit or commit them. The build compiles only *.{base,common,shared,material,bootstrap,indigo,fluent}.scss. Give helper partials a _ prefix and @use them.

Show full SKILL.md (167 more words)Show less

Validation Checklist

  • Only .scss files are in the diff
  • Load-path specifiers. Values come from the theming functions.
  • [part~='…'] selectors
  • Dark files emit only diff(light.$base, $theme)
  • New parts and custom properties are in the JSDoc and in spec.md
  • build:styles and lint:styles pass. All themes checked.
  • CHANGELOG updated if the change is user-visible

Common Pitfalls

SymptomCause / Fix
Change does not showbuild:styles did not run, or the filename is outside the glob
Change is gone after a buildA .css.ts file was edited. Edit the .scss.
Applies in one theme onlyIt is in a theme file, not in shared/[component].common.scss
Part selector stopped matching[part='x'] with a multi-name partMap
var-get() emits nothingThe key is not in the schema
Dark looks like lightdiff(light.$base, …) is missing, or an entry is missing in themes.ts
Consumers cannot overrideSpecificity is too high, or the element is not a part

Reference Examples

  • src/components/badge/themes/: a complete, compact scaffold
  • src/components/input/themes/: many parts, material notch, data-role selectors
  • src/components/rating/spec.md: parts and custom properties documented together

© IgniteUI, 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 .agents/skills/update-component-styles of IgniteUI/igniteui-webcomponents.

Open the folder on GitHubat commit ab2cd1d

Compare with similar skills

Update Component Styles 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.

Update Component Styles compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Component Styles this skillIgniteUI/igniteui-webcomponents170—~1.3kAutomated safety check: PassMIT
Tailwindcss Developmentanonaddy/anonaddy4.9k10 repos~865Automated safety check: PassMIT
UI StylingOhh-889/skyroc79513 repos~2.5kAutomated safety check: PassMIT
MCP Developmentcoollabsio/coolify63k1 repos~949Automated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
UI UX Pro Maxsaoudi-h/solar-icons18218 repos~11kAutomated safety check: NotesCustom licence

Similar skills

  • Tailwindcss Development

    anonaddy/anonaddy

    Always invoke when the user's message includes 'tailwind' in any form.

    4.9k GitHub starsUsed in 10 repos~865 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

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-check passed

  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed

  • UI UX Pro Max

    saoudi-h/solar-icons

    UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.

    182 GitHub starsUsed in 18 repos~11k tokens
    Frontend & DesignAuto-check: notes

  • Ink Tui Wizard

    novuhq/novu

    Build terminal user interfaces (TUIs) using Ink (React for CLIs) and @inkjs/ui with a reactive, session-driven wizard pattern.

    40k GitHub stars~1.9k tokensUpdated today
    Frontend & DesignAuto-check passed

More from IgniteUI/igniteui-webcomponents

All 13 skills in this repo

  • Igniteui Wc Customize Component Theme

    IgniteUI/igniteui-webcomponents

    Theme and style Ignite UI Web Components (and igniteui-react) apps using CSS custom properties, optional Sass, and the igniteui-theming MCP server.

    170 GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Igniteui Wc Generate From Image Design

    IgniteUI/igniteui-webcomponents

    Implement application views from design images (screenshots, mockups, wireframes) using Ignite UI Web Components, with the igniteui-cli and igniteui-theming MCP servers for component discovery…

    170 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Igniteui Wc Integrate With Framework

    IgniteUI/igniteui-webcomponents

    Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package…

    170 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • Add Component Property

    IgniteUI/igniteui-webcomponents

    Add a reactive property to an existing Lit web component with proper decorators, types, tests, specification updates, and documentation

    170 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Create New Component

    IgniteUI/igniteui-webcomponents

    Create a new Lit web component following project conventions, including specification, component class, styles, tests, Storybook story, and exports

    170 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Igniteui Wc Choose Components

    IgniteUI/igniteui-webcomponents

    Identify the right Ignite UI Web Components (igniteui-webcomponents, grids, charts, dock manager, React wrappers) for a UI requirement and point to official docs, examples, and API references.

    170 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

Categories

Questions about Update Component Styles

What does Update Component Styles do?

Update component styling following the SCSS to Lit CSS workflow with proper theme support. Update Component Styles is an agent skill from IgniteUI/igniteui-webcomponents.

When should I use Update Component Styles?

Update Component Styles fits situations like: tasks that involve CSS and styling.

How do I install Update Component Styles in Claude Code?

Run `npx skills add IgniteUI/igniteui-webcomponents --skill update-component-styles -a claude-code`. Or copy the skill folder (.agents/skills/update-component-styles in IgniteUI/igniteui-webcomponents) into .claude/skills/update-component-styles in your project. Claude Code loads it when a task matches its description.

How do I install Update Component Styles in Codex?

Run `npx skills add IgniteUI/igniteui-webcomponents --skill update-component-styles -a codex`. Or copy the skill folder (.agents/skills/update-component-styles in IgniteUI/igniteui-webcomponents) into .agents/skills/update-component-styles in your project. Codex loads it when a task matches its description.

Can I use Update Component Styles 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 IgniteUI/igniteui-webcomponents --skill update-component-styles -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-component-styles, .gemini/skills/update-component-styles, .github/skills/update-component-styles and .opencode/skills/update-component-styles in your project.

What does Update Component Styles need to run?

Going by SKILL.md and its folder, Update Component Styles needs the command-line tools its instructions call (npm).

Does Update Component Styles access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Update Component Styles 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 Update Component Styles use?

Update Component Styles 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 Update Component Styles use?

About 1.3k tokens (SKILL.md is roughly 5.1k 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 Update Component Styles?

Skills that share tags, products or a category with Update Component Styles: Tailwindcss Development (anonaddy/anonaddy, 4.9k stars), UI Styling (Ohh-889/skyroc, 795 stars), MCP Development (coollabsio/coolify, 63k stars) and Web Animation Design (baptisteArno/typebot.io, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update Component Styles?

IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-webcomponents, which has 170 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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