Claude Plugins

Experimental testing harness lives under experiments/claude-probe/.

A curated collection of 44 Claude Code plugins providing 400+ skills and 21 agents for development workflows.

Install the Marketplace

Install the full plugin collection as a marketplace:

claude plugin install laurigates/claude-plugins

This registers all 44 plugins. You can then enable individual plugins as needed.

Install Individual Plugins

If you prefer to install plugins one at a time:

claude plugin install laurigates-claude-plugins/<plugin-name>

For example:

claude plugin install laurigates-claude-plugins/git-plugin
claude plugin install laurigates-claude-plugins/python-plugin
claude plugin install laurigates-claude-plugins/testing-plugin

Getting Started

1. Install the marketplace using the command above
2. Run a health check — /health:check then /health:audit to diagnose your setup and get plugin recommendations for your stack
3. Follow the tiered setup — The Plugin Map provides a recommended install order (Tier 0 foundation through Tier 3+ stack-specific), decision trees, and project presets

MCP Server Setup

Use the included justfile for quick MCP server configuration:

# Set up all MCP servers and cclsp
just claude-setup

# Or install individual servers
just mcp-github
just mcp-playwright
just mcp-context7

Alternatively, use the /configure:mcp skill for interactive configuration.

Design Principles

The methodology behind these plugins — what a probabilistic agent should decide versus what a deterministic substrate should verify and remember. See docs/PRINCIPLES.md for the full set, each grounded in the rules, skills, and hooks that embody it.

Prerequisites

• Bash 5+ — Required for shell scripts. macOS ships Bash 3.2; install via brew install bash.

Plugins by Category

AI & Agents

Development

Languages

Quality & Testing

Version Control

CI/CD

Infrastructure

Documentation & Communication

UX & Components

Automation & Utilities

Game Development

Plugin Structure

Each plugin follows the standard Claude Code plugin structure:

<plugin-name>/
├── .claude-plugin/
│   └── plugin.json     # Plugin manifest
├── README.md           # Plugin documentation
├── CHANGELOG.md        # Auto-generated by release-please
├── skills/
│   └── <skill-name>/
│       └── SKILL.md    # Skill definition
└── agents/             # Agent definitions (optional)
    └── <agent>.md

Ecosystem: consumed by dotfiles

This marketplace's primary real-world consumer is laurigates/dotfiles, which installs, pins, and dogfoods the plugins via just recipes. The two repos form a provider ↔ consumer symbiosis:

flowchart LR
    subgraph cp["claude-plugins (this repo — provider)"]
        mkt["marketplace.json<br/>44 plugins"]
        skill["/configure-claude-plugins"]
        rules["shared .claude/rules/"]
    end
    subgraph df["dotfiles (consumer)"]
        pj["just plugins-*<br/>(plugins.just)"]
        pins["~/.claude/settings.json<br/>canonical pins"]
    end
    mkt -->|curl marketplace.json| pj
    skill -->|plugins-setup-repo| pj
    pj -->|install / enable| pins
    pins -->|plugins-audit drift-check| pj
    rules -.->|conventions mirrored| df

    classDef prov fill:#f3e8ff,stroke:#a855f7;
    classDef cons fill:#ffedd5,stroke:#f97316;
    class mkt,skill,rules prov;
    class pj,pins cons;

• Provider → consumer: dotfiles' plugins-install fetches this repo's marketplace.json; plugins-setup-repo runs /configure-claude-plugins to wire a target repo to the marketplace.
• Consumer → provider: plugins-audit / plugins-sync-repo compare each repo's committed enabledPlugins against the canonical pin set, exercising the marketplace as a live consumer.
• Shared conventions: conventional-commits, parallel-safe-queries, gh-json-fields, and bash-tool-replacements rules exist in both repos.

The authoritative diagram (with the full just module/group layout) lives in the consumer repo: dotfiles/docs/justfile-architecture.md. Justfile authoring/auditing for both repos is governed by this marketplace's tools-plugin:justfile-expert and configure-plugin:configure-justfile.

Development

Plugins use release-please for automated versioning. Use conventional commits to trigger releases:

feat(git-plugin): add worktree support    # minor bump
fix(python-plugin): handle empty venv     # patch bump

See CLAUDE.md for detailed development instructions.

Regenerating the Plugin List

The flat plugin list can be generated from marketplace.json:

jq -r '.plugins[] | "| **\(.name)** | \(.category) | \(.description) |"' .claude-plugin/marketplace.json

License

MIT