New: 98,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 Docs

by AgnosticUI in AgnosticUI/agnosticui

Update component documentation when code changes. An agent skill from AgnosticUI/agnosticui.

Apache-2.0Auto-check passedFrontend & Design

Install Update Component Docs

skills CLI
$ npx skills add AgnosticUI/agnosticui --skill update-component-docs -a claude-code

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

GitHub CLI
$ gh skill install AgnosticUI/agnosticui update-component-docs --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/AgnosticUI/agnosticui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/update-component-docs .claude/skills/update-component-docs && 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-docs
GitHub stars
827
Token cost
~607 tokens
SKILL.md length
241 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Apache-2.0

At a glance

Update component documentation when code changes. An agent skill from AgnosticUI/agnosticui.

  • Works in 7 steps: Locate component files → Identify what changed → Check related documentation → …
  • Frontend & Design work in your project
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Update Component Docs is an agent skill from AgnosticUI/agnosticui. Update component documentation when code changes

Its SKILL.md is about 610 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. It works with React, Vue.js, Storybook and VitePress. The repository describes itself as: AgnosticUI Local (v2) is a CLI-based UI component library that copies components directly into your project. Works with AI tools, agent-driven UIs, and prompt-ready workflows. The licence is Apache-2.0.

When your agent uses it

  • Frontend & Design work in your project

Example prompts

  • “/update-component-docs”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob

Workflow steps

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

  1. Locate component files
  2. Identify what changed
  3. Check related documentation
  4. Propose documentation updates
  5. WAIT FOR USER APPROVAL
  6. Update consistently across frameworks
  7. Verify completeness

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Update Component Docs loads about 607 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 241 words of instructions outside code blocks.

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

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 AgnosticUI/agnosticui at commit c028c27, republished under its Apache-2.0 licence (© AgnosticUI). 241 words, ~607 tokens.

Download SKILL.mdSave it as .claude/skills/update-component-docs/SKILL.md (or your agent's skills folder).
name
update-component-docs
description
Update component documentation when code changes
allowed-tools
Read, Grep, Glob
disable-model-invocation
true

Usage: /update-component-docs COMPONENT_NAME

Examples:

  • /update-component-docs button
  • /update-component-docs alert

Update docs for component: $ARGUMENTS

Setup:

  1. Read .claude/PROJECT_CONTEXT.md for AgnosticUI structure and paths

Process:

  1. Locate component files:
   Read v2/lib/src/components/$ARGUMENTS*
   Read v2/site/docs/components/$ARGUMENTS.md
   Glob v2/playgrounds/*/src/stories/*$ARGUMENTS*
   Glob v2/examples/*/src/*$ARGUMENTS*

  1. Identify what changed:

    • Core component API (props, slots, events)
    • CSS custom properties or design tokens
    • Behavior or interaction patterns
    • Accessibility features
    • Breaking changes vs additions

  2. Check related documentation:

    • VitePress component page for API tables and usage examples
    • Storybook stories across Lit, React, and Vue playgrounds
    • Example implementations in each framework
    • Related playbook if component has specific use case docs
    • Design tokens if styling/theming changed

  3. Propose documentation updates:

    • VitePress: Update props tables, events, slots, CSS custom properties, usage examples
    • Storybook stories: Update args, controls, story descriptions across all three frameworks
    • Examples: Verify examples still work with new API
    • Playbooks: Update if related to specific workflow/pattern
    • Design tokens: Note if component uses new/changed tokens

  4. WAIT FOR USER APPROVAL

  5. Update consistently across frameworks:

    • Ensure Lit, React, and Vue stories show equivalent functionality
    • Use framework-appropriate syntax but consistent examples
    • Same terminology and descriptions across all docs
    • Code examples match current API
    • Note framework-specific differences where relevant

  6. Verify completeness:

    • All frameworks (Lit, React, Vue) documented
    • VitePress and Storybook in sync
    • Examples updated if API changed
    • Design token references accurate

Token Optimization:

  • Start with core component to understand changes
  • Only read framework-specific files if API differs by framework
  • Skip playbooks unless component has dedicated workflow docs
  • Check design tokens only if styling/theming aspects changed

© AgnosticUI, Apache-2.0. 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 .claude/skills/update-component-docs of AgnosticUI/agnosticui.

Open the folder on GitHubat commit c028c27

Compare with similar skills

Update Component Docs 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 Docs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update Component Docs this skillAgnosticUI/agnosticui827—~607Automated safety check: PassApache-2.0
Storybook Checkrstackjs/storybook-rsbuild156—~2.5kAutomated safety check: PassMIT
Storybook Syncrstackjs/storybook-rsbuild156—~5.2kAutomated safety check: PassMIT
Framework Interopinkline/inkline1.5k—~1.3kAutomated safety check: PassNone
GSAP Core Animationgreensock/gsap-skills16k4 repos~3.7kAutomated safety check: PassMIT
Boneyard0xGF/boneyard7.5k—~2.2kAutomated safety check: NotesMIT

Similar skills

  • Storybook Check

    rstackjs/storybook-rsbuild

    Audit ported storybook-rsbuild source files against the CURRENT upstream Storybook source, grouped by the local package that owns each port, independent of commit history.

    156 GitHub stars~2.5k tokensUpdated 8 days ago
    Frontend & DesignAuto-check passed

  • Storybook Sync

    rstackjs/storybook-rsbuild

    Check and analyze upstream Storybook repository changes that may need to be synced to storybook-rsbuild.

    156 GitHub stars~5.2k tokensUpdated 8 days ago
    Frontend & DesignAuto-check passed

  • Framework Interop

    inkline/inkline

    The seven framework output packages and the boundaries Inkline lives on — exports contracts, peer-dep/version matrix, per-target capability gaps, idiom fidelity, and the styleframe upstream…

    1.5k GitHub stars~1.3k tokensUpdated 27 days ago
    Frontend & DesignAuto-check passed

  • GSAP Core Animation

    greensock/gsap-skills

    Covers the GSAP core API for tweens, easing, staggers, defaults and matchMedia, and when to choose GSAP over CSS animations or other JavaScript animation libraries.

    16k GitHub starsUsed in 4 repos~3.7k tokens
    Frontend & DesignAuto-check passed

  • Boneyard

    0xGF/boneyard

    Use boneyard-js to add, configure, debug, or rebuild skeleton screens.

    7.5k GitHub stars~2.2k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check: notes

  • Kill AI Slop

    yetone/kill-ai-slop

    Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

    1.3k GitHub stars~1.4k tokensUpdated 23 days ago
    Frontend & DesignAuto-check passed

More from AgnosticUI/agnosticui

  • Implement GitHub Feature

    AgnosticUI/agnosticui

    Design and implement a new feature or component from a GitHub issue.

    827 GitHub stars~1.6k tokensUpdated 3 mo ago
    Auto-check passed

  • Implement Ag Playbook

    AgnosticUI/agnosticui

    Implement a playbook from its PROMPT specification files. An agent skill from AgnosticUI/agnosticui.

    827 GitHub stars~1.7k tokensUpdated 3 mo ago
    Auto-check passed

  • Check Accessibility

    AgnosticUI/agnosticui

    Review component for accessibility issues. An agent skill from AgnosticUI/agnosticui.

    827 GitHub stars~635 tokensUpdated 3 mo ago
    Auto-check passed

  • Fix GitHub Issue

    AgnosticUI/agnosticui

    Fix a GitHub issue by number. An agent skill from AgnosticUI/agnosticui.

    827 GitHub stars~751 tokensUpdated 3 mo ago
    Auto-check passed

  • Explain Code

    AgnosticUI/agnosticui

    Explain what code does in plain English

    827 GitHub starsUsed in 1 repo~507 tokens
    Auto-check passed

Works with

Categories

Questions about Update Component Docs

What does Update Component Docs do?

Update component documentation when code changes. An agent skill from AgnosticUI/agnosticui. Update Component Docs is an agent skill from AgnosticUI/agnosticui.

When should I use Update Component Docs?

Update Component Docs fits situations like: frontend & Design work in your project.

How do I install Update Component Docs in Claude Code?

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

How do I install Update Component Docs in Codex?

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

Can I use Update Component Docs 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 AgnosticUI/agnosticui --skill update-component-docs -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-docs, .gemini/skills/update-component-docs, .github/skills/update-component-docs and .opencode/skills/update-component-docs in your project.

What does Update Component Docs need to run?

SKILL.md names no scripts, command-line tools or credentials: Update Component Docs is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob.

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

Update Component Docs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Update Component Docs use?

About 607 tokens (SKILL.md is roughly 2.4k 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 Docs?

Skills that share tags, products or a category with Update Component Docs: Storybook Check (rstackjs/storybook-rsbuild, 156 stars), Storybook Sync (rstackjs/storybook-rsbuild, 156 stars), Framework Interop (inkline/inkline, 1.5k stars) and GSAP Core Animation (greensock/gsap-skills, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Update Component Docs?

AgnosticUI (a GitHub organization) maintains it in AgnosticUI/agnosticui, which has 827 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on June 30, 2026.

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