AugmentClaude

Code Explainer

Explain what code does in plain English.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/explain-code-agnosticui/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Explain what code does in plain English

What this skill does

Usage: /explain-code PATH_OR_DESCRIPTION

Examples:

  • /explain-code v2/lib/src/components/Button.ts
  • /explain-code the button ripple effect
  • /explain-code design token system

Explain: $ARGUMENTS

Setup:

  1. Read .claude/PROJECT_CONTEXT.md to understand AgnosticUI's architecture

Process:

  1. Locate and read the code:

    • Identify if it's a core component, framework implementation, or utility
    • Read the specified file(s)
    • Use Grep/Glob to find related files if needed:
      • If explaining core component, show framework usage examples
      • If explaining framework story, reference core component
      • If explaining utility, show where it's used
  2. Understand the context:

    • Where does this fit in AgnosticUI's architecture?
    • Is it framework-agnostic or framework-specific?
    • Does it use design tokens or CSS custom properties?
    • Are there related files in other frameworks?
  3. Explain clearly:

    • What it does (high level, user-facing behavior)
    • How it works (key logic, algorithms, patterns)
    • Why it's structured this way (architectural decisions)
    • AgnosticUI-specific context:
      • How it fits the CSS-first approach
      • Framework-agnostic vs framework-specific aspects
      • Design token usage
      • Accessibility considerations
    • Common usage patterns with examples
    • Edge cases or gotchas to be aware of
  4. Provide helpful context:

    • Show where it's used (examples, stories, playgrounds)
    • Note framework differences if applicable
    • Link to related components or utilities
    • Reference relevant playbooks if they exist

Keep explanations:

  • Clear and jargon-free (or explain jargon)
  • Organized from high-level to details
  • Focused on understanding, not just describing
  • Contextualized within AgnosticUI's multi-framework architecture

Related skills