Examples

The examples/ directory in the repo holds runnable sources, each a small but valid mind source with its own README.md and a test that melds it so it cannot rot. This page maps each use case, consumer and maintainer, to the example that demonstrates it.

Every example is a directory inside the mind repo, not its own git repo, so clone the repo, copy the example out, and init a repo before melding (each README shows the exact commands):

git clone --depth 1 https://github.com/jaemk/mind /tmp/mind-repo
cp -r /tmp/mind-repo/examples/<name> /tmp/<name>-demo
cd /tmp/<name>-demo && git init -q && git add -A && git commit -qm init
mind meld /tmp/<name>-demo
mind probe

Example catalog

Consumer use cases

You are installing and managing tooling that other people authored.

• Install an item from a source. Meld a repo, then learn an item. See the Quickstart and the starter example (mind meld, mind learn).
• Browse and search what is available. mind probe opens an interactive browser, or prints a listing when piped. See Commands.
• Resolve a name collision between two sources. Namespace one on install with mind meld <repo> --namespace <prefix>, so its items install as <prefix>:<name>. See namespacing and Troubleshooting.
• Pull from a curated registry. Meld a super-source to register a whole chain of repos at once; meld --recursive offers every nested source for install. See super-source.
• Meld a Claude plugin or marketplace. A repo with a .claude-plugin/plugin.json or .claude-plugin/marketplace.json melds with no re-packaging; its skills and agents show up as items. See Claude plugin marketplaces and the marketplace-plugin / marketplace-catalog examples.
• Install into more than one agent home. Configure lobes in ~/.mind/config.toml. See Configuration and multi-lobe.
• Stay up to date. mind sync refreshes every source; mind upgrade upgrades installed items and reports deltas first. See Commands and drift.
• Claim an unmanaged lobe item into a managed source. mind absorb moves a file you placed in a lobe by hand into a source you own and installs it as a managed item. See absorb and the absorb example.
• Run under an enterprise policy. A fixed-path managed policy restricts a client to trusted sources and locks related settings. See policy.

Maintainer use cases

You are authoring a source repo for others to meld.

• Ship items with zero config. Use the convention layout; no mind.toml needed. See Source layout and starter.
• Declare an explicit inventory, or control what is exported. List items with [[items]] to turn convention off, set custom path/link, and omit files you do not want offered. See explicit.
• Lay out a monorepo or subtree. Point [source].roots at the package subtrees, or use [discover] kind globs for layouts roots cannot express. See monorepo and discover.
• Share helper tooling across items. Ship a tool item and reference it with {{tools:name}} / {{path:ref}}, or bundle a script with one skill and address it with {{self}}. See tooling and Source layout.
• Build or install tooling at meld. Declare a source [[hooks]] install entry (and an uninstall entry for teardown). See Install hooks and hooks.
• Run a host side effect per item. Declare per-item install/uninstall hooks (or [[items.hooks]]). See explicit.
• Make intra-source references survive a prefix. Write sibling references as {{ns:name}} tokens. See namespacing and Authoring a source.
• Curate other repos into a registry. List them in [discover].sources; a bare list keeps your own convention items too. See super-source; for a repo that is both a Claude marketplace and a curator, see marketplace-curator.
• Validate and scaffold before publishing. mind init-source scaffolds a mind.toml and reports references; mind review validates a source. See Authoring a source.