Video summary

The Claude VS Code Setup I Actually Use (Plugins, Skills, and CLAUDE.md) [Part 15]

Main summary

Key takeaways

Technology

Main focus: Setting up Claude in VS Code (Claude VS Code extension)

  • The speaker demonstrates a “Claude” setup specifically using the VS Code Claude extension.
  • They use the extension to generate a CLAUDE.md agent file, instructing Claude to “set me up” with that file.
  • Running this later (mid-project) is beneficial because it gives Claude full project context (including all changes/tweaks already made).
    • The speaker contrasts this with running it earlier (e.g., during PRD work), which would have produced a less accurate/complete CLAUDE.md.

Why timing matters (context quality)

  • The speaker notes that the architecture/context understanding is much better once the project evolves.
  • Their concern about not doing it at the start is reduced because the system is mostly made of atomic, relatively self-contained scripts (unlike a highly interdependent app such as a React project).
  • Even if scripts are complex, they believe it’s not overly difficult for an agent to navigate.

Claude VS Code Extension: Plugins (how to install and manage)

  • In the Claude VS Code extension, plugins are managed via a slash command:
    • /plugins → Manage plugins
  • First run behavior
    • The plugins list is empty initially.
    • The marketplace UI doesn’t clearly explain setup, so the speaker had to Google how to do it.
  • Plugin installation method
    • You provide a GitHub URL to add a plugin.
    • After adding, the UI allows you to select and install multiple plugins.

Skills and slash commands

  • Installed skills/plugins expose additional slash commands inside VS Code.
  • The speaker shows invoking skills via / commands, where skills can perform agent actions and drive workflow.
  • One mentioned skill (example) includes: “stripe superbase hugging face”, listed among things the speaker intends to use for other projects.

Specific skills/plugins mentioned (examples)

The subtitles indicate these items as installed/available:

  • A “superpower skill”
    • Requires approval for every command
    • Was observed doing Git-related actions
    • The speaker says they might disable/kill it later
  • Feature dev (unclear whether it uses GitHub or standard git)
  • Front end design (intended use for future projects)

Where this series is going

  • The speaker concludes this episode is only about Claude setup:
    • Claude + VS Code extension
    • including CLAUDE.md, plugins, and skills
  • UI work is promised for the next video.

Main sources / speakers

  • Primary speaker: The YouTube video host/author, speaking throughout the subtitles and discussing their VS Code + Claude workflow and configuration.

Original video