Object-Core

What it is

ObjectCore is a plugin marketplace that builds itself. Instead of hand-authoring Claude Code plugins one at a time, ObjectCore is the factory: a pipeline that takes plugin specs in and produces governed, tested, versioned plugins out — then publishes and maintains them in a public registry.

The output isn’t the plugins. It’s the system that produces and governs plugins.

The registry is live

The catalog serves from registry.objectcore.ai and installs into Claude Code in one line:

/plugin marketplace add https://registry.objectcore.ai/v1/marketplace.json

Thirteen plugins are live, all MIT-licensed. A few from the current generation:

• commit-craft / pr-craft — conventional commit messages from staged changes; PR titles and descriptions from branch commits
• kb-writer — surfaces project knowledge at session start, captures durable lessons at conclusion
• design-forge — authors stack-agnostic design systems with DTCG tokens, accessible scales, and theme resolution
• hello-objectcore — the minimal example validating the derive-and-validate pipeline

The more interesting half of the catalog is the factory itself.

The factory loop

Four meta-plugins run the production line, and each is itself a plugin in the marketplace:

1. plugin-forge — generates new plugins from specs via the /forge pipeline: planning, scaffolding, validation, activation
2. plugin-validator — a hard-rule checklist plus an eval gate; nothing publishes without passing
3. release-manager — Changesets-driven versioning, semantic tagging, SHA-pinned publishing, provenance attestation
4. marketplace-builder — derives marketplace.json from the plugin graph and keeps the registry synchronized

Specs in, governed plugins out. When the pipeline improves, every future plugin improves with it.

The self-improvement layer

Three plugins close the loop on the factory’s own quality:

• reflection — a PostToolUse hook that auto-invokes a self-reflection subagent when a gate fails, diagnosing the issue and capturing the lesson
• knowledge-base — the factory’s durable memory of lessons, patterns, gotchas, and decisions
• forge-improver — proposes behavior-preserving refinements to the scaffolder, admitted only through eval-driven review

And meta-generator takes it one level up: it generates new meta-plugins from an archetype. The factory replicates itself.

Why a factory

Plugin ecosystems fail in one of two ways: they stay tiny because authoring is manual, or they sprawl because nothing enforces a standard. A factory solves both. Throughput comes from generation; trust comes from the gates every artifact must pass — validation, evals, provenance. The failure gets diagnosed, the lesson gets kept, and the next plugin is built to a higher standard.

Status

Alpha. The registry is live with the first generation of 13 plugins, and the factory is producing more. Add the marketplace and try them, or watch the blog for build notes.