Claude Code Integration

Claude Code has the deepest integration with Skills Playground. You can install skills with a single command, add them to your CLAUDE.md file, or use them as plugins for on-demand invocation.

Install with One Command

Every skill on Skills Playground includes an install command. Run it in your terminal and the skill is added to your project's .claude/skills/ directory:

# Install a skill from Skills Playground
claude install-skill https://skillsplayground.com/skills/nextjs-developer/

Once installed, the skill becomes available as a slash command in Claude Code. Type / in the chat to see your installed skills.

Add to CLAUDE.md

For instructions that should always be active, add the skill's system prompt to your CLAUDE.md file at the project root:

# CLAUDE.md

## Project Overview
E-commerce API built with Node.js and TypeScript.

## Conventions
- Named exports, never default exports
- All async handlers wrapped with asyncHandler()
- API responses follow: { data, error, meta }
- Prefer early returns over nested conditionals

## Testing
- Colocate tests: feature.ts -> feature.test.ts
- Integration tests use test database, never mock Prisma

CLAUDE.md is loaded automatically at the start of every Claude Code session. The instructions apply to all interactions without needing to invoke a slash command.

Claude Code supports multiple CLAUDE.md locations:

• CLAUDE.md -- Project root, shared with team via git
• .claude/CLAUDE.md -- User-specific project settings (gitignored)
• ~/.claude/CLAUDE.md -- Global preferences across all projects
• Subdirectories -- apps/api/CLAUDE.md for directory-specific rules

Skills as Slash Commands

When you install a skill, it creates a Markdown file in .claude/skills/. These skills are invoked on demand via slash commands:

.claude/
  skills/
    nextjs-developer.md    # /nextjs-developer
    code-reviewer.md       # /code-reviewer
    test-writer.md         # /test-writer

Skills are different from CLAUDE.md -- they are activated when you need them rather than being always on. This keeps your context window efficient by only loading relevant instructions.

Plugins

Claude Code plugins extend functionality beyond system prompts. Plugins can include skills, hooks, MCP server configurations, and more. If a skill provides a plugin, you can install it with:

# Install a plugin
claude plugin add <plugin-name>

Plugins are useful when a skill needs more than just instructions -- for example, when it requires specific MCP servers or custom hooks to work properly. See the Claude Code Plugins Guide for details.

Which Method to Use

• CLAUDE.md -- For always-on project instructions (tech stack, conventions, architecture). Start here.
• Installed skills -- For task-specific workflows you invoke on demand (code review, test writing, deployment).
• Plugins -- For skills that bundle additional tooling (MCP servers, hooks, configurations).

Most projects benefit from a combination: a CLAUDE.md with core conventions plus a few installed skills for specialized tasks.

Browse the skills directory to find skills for your project, or read the CLAUDE.md Guide for a complete reference.