Documentation

Getting Started

A complete guide to installing and using Claude Playground assets in your workflow.

Prerequisites

Before using Claude Playground, you need Claude Code installed on your machine.

Install Claude Code

Follow the official installation guide from Anthropic. Claude Code works on macOS and Linux.

Verify it works

Open your terminal and run claude --version. You should see the version number printed.

Have git installed

The installer uses git to fetch assets. Run git --version to confirm it's available.

What is Claude Playground

Claude Code is Anthropic's CLI for working with Claude in your terminal and IDE. It reads files, runs commands, and follows project-specific instructions—but it's only as useful as the context you give it.

Claude Playground is a curated library of pre-built assets that give Claude Code instant context: coding workflows, project conventions, and task-specific instructions. Instead of writing everything from scratch, install what you need and start working.

The three asset types

Every asset in Claude Playground is one of three types. Each serves a different purpose and installs to a different location.

Skills

Skills are SKILL.md files that teach Claude specific workflows. They live in ~/.claude/skills/ and are automatically available in every Claude Code session, regardless of which project you're in.

When you invoke a skill (e.g., type /review in Claude Code), Claude reads the SKILL.md file and follows its instructions. Skills can define structured processes like severity-rated code reviews, PR description templates, or step-by-step framework migrations.

~/.claude/skills/

code-review/ SKILL.md

pr-description/ SKILL.md

angular-upgrade/ SKILL.md

Templates

Templates are CLAUDE.md files you drop into a project root. When Claude Code starts a session, it reads CLAUDE.md and treats it as project-level context—your conventions, directory structure, testing patterns, and preferred approaches.

Think of templates as onboarding docs for your AI pair programmer. A good CLAUDE.md means Claude immediately knows how your project is organized, which frameworks you use, and how you prefer things done. Use a template as a starting point and customize it for your project.

your-project/

CLAUDE.md ← installed here

src/

package.json

Prompts

Prompts are standalone instructions you paste directly into a Claude conversation. Unlike skills (which are persistent and automatic), prompts are one-shot and on-demand. Use them when you want consistent results for a specific task without installing anything permanently.

Prompts are great for tasks you do occasionally: setting up Storybook in a new project, configuring browser testing, or getting a structured codebase tour. Copy the prompt, paste it into Claude Code, and it handles the rest.

Installing assets

The interactive installer handles everything. Run one command and pick what you want.

terminal

$curl -fsSL claude.sporich.dev/install.sh | bash

What happens when you run it

Clones the repository

The installer fetches the latest assets from GitHub into a cache at ~/.claude-playground. Subsequent runs pull updates automatically.

Presents a menu

You'll see a numbered list of all available assets grouped by category. Enter the numbers of the ones you want, or type all to install everything.

Installs to the right locations

Skills are symlinked to ~/.claude/skills/. Templates are copied as CLAUDE.md in your current directory. Prompts are printed to the terminal or saved to a file.

Shows a summary

After installation, you'll see exactly what was installed and where it went.

Try it out

Here's a quick way to see Claude Playground in action: install the code-review skill and use it immediately.

Run the installer and select the code-review skill

$ curl -fsSL claude.sporich.dev/install.sh | bash

Open Claude Code in any project

$ cd your-project && claude

Ask Claude to review your code

Claude will automatically use the code-review skill to give you a structured review with severity ratings, specific file references, and actionable suggestions.

Where things go

A quick reference for where each asset type lives on your system.

Type	Location	Scope
Skills	~/.claude/skills/<name>/SKILL.md	Global — all sessions
Templates	./CLAUDE.md	Project-level
Prompts	copy & paste	One-shot

Contributing

Want to add your own asset? The process is simple:

1Create a .md file in the right directory (skills/<category>/<name>/SKILL.md, templates/<category>/<name>.md, or prompts/<category>/<name>.md).
2Add YAML frontmatter with name, description, and tags.
3Run bash scripts/build-catalog.sh to regenerate the catalog and verify your asset appears.
4Submit a PR to the GitHub repo.