OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

AI index

Plugin authoring templates

Scaffold focused Cursor plugins for ContractSpec product and core libraries.

Create a focused plugin

Start from a scoped domain and keep each plugin aligned to one product or library surface.

catalog-authoring-layout
packages/apps-registry/cursor-marketplace/
  plugins/
    <plugin-name>/
      .cursor-plugin/plugin.json
      rules/
      commands/
      agents/
      skills/
      .mcp.json

Template outputs

  • .cursor-plugin/plugin.json with plugin metadata and paths
  • rules/, commands/, agents/, and skills/ content directories
  • .mcp.json with all MCP server declarations used by the plugin
  • README.md describing scope and governance boundaries

Validate before submission

validate-marketplace-catalog
# Validate all plugins referenced by root marketplace manifest
bun run plugin:contractspec:validate

# Optional in offline environments
SKIP_PLUGIN_NETWORK_CHECK=1 bun run plugin:contractspec:validate

Need evidence-backed template iteration?

Studio helps teams prioritize template changes from real product signals and export implementation-ready task packs.

See what Studio adds
Marketplace plugins Marketplace manifest
OSS docsStart with OSS. Adopt Studio when you want the operating layer.

Why ContractSpec

Keep educational and comparison content reachable without letting it define the primary OSS learning path.

ManifestoContract-first APISpec-driven development