Claude Connoisseur

A Claude Code plugin that brings together skills, rules, and hooks with OpenSpec's spec-driven workflow, curated with a taste for good coding.

Tip: This plugin works even better when paired with OpenSpec — a lightweight spec framework that aligns developers and AI assistants on requirements before implementation.

Installation

Add the marketplace and install the plugin from within Claude Code:

/plugin marketplace add eugeniosegala/claude-connoisseur
/plugin install claude-connoisseur@eugeniosegala-claude-connoisseur

To also install OpenSpec, see the OpenSpec installation guide. To enable extended commands like /opsx:verify or /opsx:sync, run openspec config profile and select the expanded workflow.

Updating

Third-party plugins do not auto-update by default. To get the latest version:

/plugin update claude-connoisseur@eugeniosegala-claude-connoisseur

To enable auto-updates, open /plugin → Marketplaces tab → select the marketplace → Enable auto-update.

Notes

Skills are shown as /codex-review, /functional, etc. in the command palette. The full namespaced form ( /claude-connoisseur:codex-review) also works if you need to disambiguate from other plugins.
The auto-format hook runs automatically after every Write or Edit — formatters are detected at runtime, so if a formatter isn't installed it is silently skipped.

Rules are not distributed via the plugin system. To use the coding-style rule, copy it manually into your project:

mkdir -p .claude/rules
curl -o .claude/rules/coding-style.md https://raw.githubusercontent.com/eugeniosegala/claude-connoisseur/refs/heads/main/rules/coding-style.md

Example workflows

flowchart TD
    Start(["🚀 Start task"]) --> Decision{"Non-trivial?\nNew feature,\nmulti-file change"}
    Decision -- Yes --> Propose["Spec the feature\n/opsx:propose"]
    Decision -- No --> Describe["Describe the task to the agent in the chat or use Skills\n/functional, /object-oriented, etc..."]
    Propose --> Review["Review the plan manually and with other agents (optional)\n/codex-review"]
    Review --> Apply["Implement with\n/opsx:apply\nhooks run automatically"]
    Apply --> QualityGates["Quality gates (optional)\n/object-oriented, /perf-review, etc..."]
    QualityGates --> Issues{"Issues\nfound?"}
    Issues -- Yes --> Fix["Fix code or\nrun other Skills to fix the problem"]
    Fix --> Issues
    Issues -- No --> Verify["Re-verify against spec\n/opsx:verify"]
    Verify --> Archive["Archive spec\n/opsx:archive"]
    Archive --> Done(["✅ Done"])
    Describe --> Hooks["Claude refactors code\nhooks handle formatting + type-checking"]
    Hooks --> TestRunner["Verify tests\n/test-runner"]
    TestRunner --> OptReview["Perf review (optional)\n/perf-review"]
    OptReview --> Done

With OpenSpec — building a feature end to end

Best for non-trivial work: new features, multi-file changes, or anything that benefits from upfront requirements.

Spec the feature — OpenSpec creates a proposal, specs, design, and task checklist:
```
/opsx:propose Add Stripe billing for subscription management
```
Review the plan (optional) — read the generated artefacts, refine if needed, then get a second opinion:
```
/codex-review review the OpenSpec proposal and technical design
```
Implement — OpenSpec works through the task checklist and writes code (hooks run automatically):
```
/opsx:apply
```

Quality gates — change, review, and test if needed:

# change
/object-oriented @payment_handler.ts

# review
/perf-review @payment_handler.ts database query patterns

# test
/testify @payment_handler.ts

Iterate — if the quality gate surface issues; fix the code, run other skills and re-verify against the spec:
```
/opsx:verify
```
Repeat steps 4–5 until the code and the spec are aligned.
Archive — store the spec for future reference:
```
/opsx:archive
```

Without OpenSpec — quick targeted tasks

Best for contained work: a bug fix, a single-file refactor, or a quick review before a PR.

Describe the task in chat:

/functional @order-service.ts convert to pure functions and immutable data

Claude refactors the code — hooks handle formatting and type-checking automatically.
Verify — run the relevant tests:
```
/test-runner src/orders/
```

Optional review — catch anything you might have missed:

/perf-review @order-service.ts check the refactor didn't introduce performance regressions

What's included

Rules