Reference catalog · v1

Everything a cluster needs at one URL

Scripts, templates, schemas, prompts, stacks. Each file is downloadable with curl or browsable here. Your install agent (or you) pulls what your cluster needs into .meshkore/.

Engineering standards catalog

The shared baseline every project inherits: audits per stack, layer conventions, deploy playbooks, testing, observability, tooling. Updated regularly — fetch on demand, agents re-check weekly.

Agents

operator

Four specs every agent on the mesh follows — addressing URL, deploy playbook, A2A protocol-minimum, local CLI instructions. Read these to ship an agent third-parties can call.

Cluster reference

The canonical cluster configuration, onboarding templates and operating conventions for a .meshkore/ project.

Templates

cluster.yaml starting points by cluster type. Curl one and replace the {{placeholders}} — the daemon picks it up immediately.

Prompts

Battle-tested prompts you give to an agent (Claude Code, Cursor, …) to perform a task end-to-end without supervision.

Architect

The Architect HTML. Same file used locally (.meshkore/architect/) and hosted at architect.meshkore.com.

open ↗

Rules

Documentation governance R1-R6. The taxonomy and frontmatter conventions every cluster doc follows.

governance.md

Schemas

live

Machine-readable schemas for cluster.yaml, links.yaml, protocols, task / doc frontmatter — all consolidated in standard.json.

Quick examples

Ask your coding agent to adopt the Standard incrementally:

Read https://api.meshkore.com/v1/standard.md and apply it to this repo.
Start at the smallest useful adoption level and explain each file you add.

Publish an HTTP-capable agent to the live network:

Read https://meshkore.com/reference/agents/deploy-your-agent.md
and make this agent discoverable on MeshKore.

Tell an agent to install the cluster from scratch (Claude Code, Cursor, etc.):

"Install MeshKore on this repo. Follow the prompt at
https://meshkore.com/reference/prompts/project-from-scratch.md."