lpclaude-marketplace

My Claude Code Configuration (Example Repository)

This is my personal Claude Code configuration that I maintain in Git. I'm sharing it publicly as an example of how to organize and version-control a Claude Code setup. This system works for me and my needs, but might not work for others. My requirements are:

1. Make components available globally - Have my slash commands, agents, hooks, etc. accessible across all projects I work on
2. Source control everything - Version control these components for history, backup, and evolution tracking
3. Multi-machine sync - Use the same setup on multiple machines and systems seamlessly
4. Learn by doing - Continue learning about agentic systems by experimenting with different patterns
5. Share and improve - Document my approach for others and gather feedback to improve

What this is: My personal collection of agents, slash commands, and tools that I use across all my projects.

What this isn't: A framework or product to install. It's one person's configuration shared as a reference.

Why I'm Sharing This

Claude Code supports personal configurations via ~/.claude/, but there aren't many examples of how to organize and maintain them. This repository shows:

• How I structure my configuration for maintainability
• How I use Git to version control and sync across machines
• Examples of agents, slash commands, and hooks I've found useful
• Patterns for organizing a growing collection of Claude customizations

Installation Options

Option 1: Install as Plugin (Recommended)

The easiest way to use this configuration is via Claude Code's plugin system.

Quick Install:

1. In Claude Code, type /plugin and select "Add marketplace"
2. Enter: https://github.com/lpasqualis/lpclaude
3. Type /plugin again and select "Install plugin"
4. Choose lpclaude-config from the list
5. Restart Claude Code

Or use commands directly:

# Step 1: Add the marketplace (HTTPS format recommended)
/plugin marketplace add https://github.com/lpasqualis/lpclaude

# Step 2: Install the plugin
/plugin install lpclaude-config

Or skip the marketplace and install directly:

/plugin install https://github.com/lpasqualis/lpclaude

Benefits:

• ✅ One-command installation
• ✅ Automatic updates via plugin system
• ✅ Easy to enable/disable without uninstalling
• ✅ No manual symlink management
• ✅ Works alongside your personal ~/.claude/ configs

See PLUGIN_INSTALL.md for detailed plugin documentation.

Option 2: Traditional Setup (Manual Control)

For full control over files and symlinks:

git clone https://github.com/lpasqualis/lpclaude.git ~/.lpclaude
cd ~/.lpclaude
./setup.sh

See "If You Want to Try My Components" section below for details.

Option 3: Browse and Learn

Not ready to install? You can also:

As a Reference

Browse the repository to:

• See how to structure your own Claude configuration
• Get ideas for agents and slash commands you might want to create
• Learn the syntax and patterns for different component types
• Understand how various Claude Code features work together

Copy Individual Components

If you find something useful:

1. Copy the specific file to your own ~/.claude/ directory
2. Customize it for your needs
3. Make it yours - don't just use my configuration as-is

Fork as a Starting Point

To create your own configuration repository:

1. Fork this repo
2. Delete my specific configurations
3. Add your own agents, slash commands, and preferences
4. Maintain your own version-controlled Claude setup

What's in My Configuration

Here's what I've built for my workflow (yours will be different):

• Slash Commands (30+) - My shortcuts for git, documentation, job processing, learning capture, VS Code theming
• Agents - Auto-triggering helpers I use for security reviews, documentation, task queueing
• Workers - My custom pattern: reusable task templates that slash commands can run in parallel (not a Claude feature)
• Hooks - Shell scripts that prevent me from making mistakes (like cd'ing to wrong directories)
• Output Styles - How I prefer Claude to format responses for different contexts
• Status Line - My terminal prompt integration showing session context
• Utility Scripts - Helper tools like my addjob task queuing system
• Directives - General directives split into numbered files, compiled into CLAUDE.md (see Directives Compilation below)
• Resources - Research and documentation I've collected about Claude Code patterns
• Organization - How I structure everything to stay maintainable