agentleFS
Sign inStart free
AgnosticUIAgnosticUI/agnosticui/.claude/skills/update-component-docs/SKILL.md

update-component-docs

Skill833 starsChanged 9 months agoApache-2.0View on GitHub

Update component documentation when code changes

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update docs for component: $ARGUMENTS

    line 14
  2. Very specific:

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

    line 17
  3. Distinctive:

    VitePress: Update props tables, events, slots, CSS custom properties, usage examples

    line 44
  4. Distinctive:

    Storybook stories: Update args, controls, story descriptions across all three frameworks

    line 45
  5. Distinctive:

    Examples: Verify examples still work with new API

    line 46
  6. Distinctive:

    Playbooks: Update if related to specific workflow/pattern

    line 47
  7. Distinctive:

    Ensure Lit, React, and Vue stories show equivalent functionality

    line 53
  8. Distinctive:

    Use framework-appropriate syntax but consistent examples

    line 54
  9. Distinctive:

    All frameworks (Lit, React, Vue) documented

    line 60
  10. Distinctive:

    Start with core component to understand changes

    line 66
  11. Distinctive:

    Only read framework-specific files if API differs by framework

    line 67
  12. Distinctive:

    Check design tokens only if styling/theming aspects changed

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free