Plugins that teach Claude Code and Cursor a specific job:
openEHR modelling, spec-driven development,
Go and PHP standards, and documentation.
MIT-licensed. Every entry names a release tag, so an install is never a branch tip. Cursor installs each plugin from its own repository.
Loads the relevant implementation guide before it answers, and searches CKM for archetypes and templates through a hosted MCP server. Covers archetypes, templates, compositions, and AQL.
For the people who build the openEHR Assistant: authoring guides, prompts, MCP tools, and examples, and cutting releases of the server and plugin.
Each skill names the tool that enforces a rule (gofmt, go vet, golangci-lint) and cites the style guide a judgement call comes from. A reviewer agent reports what the linters miss.
PER Coding Style, PHPStan level 8, and PHP 8.4 idioms. A reviewer agent reports what the tools miss.
sdd-check follows the chain from requirement to specification, ADR, code, and test in both directions, and fails the build on drift. The delivery pipeline runs on the same documents.
Refuses to invent a statistic, testimonial, or superlative, and runs Vale on what it writes when Vale is installed. Covers technical writing, copy editing, AI-tell cleanup, SEO, and AI citability.
Each entry names a version and the matching vX.Y.Z tag. A plugin that tags a release reaches nobody until this catalog moves, and a check fails the build when an entry's version and tag disagree.
Add the marketplace once. After that, every install is <plugin>@cadasto, and an update is /plugin marketplace update cadasto followed by /plugin update <plugin>. You get the version this catalog names, not a branch tip.
Each plugin ships a manifest for both hosts from one set of skills and agents. Claude Code installs from this catalog. On Cursor, you install from the plugin's own repository.
Every plugin lives in its own repository under the MIT licence. This repository holds only the catalog and this site, and the site fetches each plugin's README at its pinned tag.
Most plugins are Markdown and JSON with no build step. The ones that use more, such as a hosted MCP server, a Go toolchain, or Python for the drift gate, say so on Choose a plugin.
CI validates the manifest and its Cursor copy, and runs a prose check over the docs, on every pull request and every push to main. Claude Code users track main, so a broken manifest would be live at once.
Install each plugin from its own repository. Importing this catalog finds nothing to install.
/plugin marketplace add Cadasto/plugin-marketplace
/plugin install <plugin>@cadasto
Restart the session to load the plugin. Not sure which one? Choose by job, or read how updates and Cursor work.