Every instruction set Kumo sells
is published publicly.

Not a summary. Not an overview. The actual files — system prompts, persona definitions, behavioral guidelines — everything that makes a kit work.

Why we do this

You can audit before you buy.

Read the repo. If a kit looks thin or poorly reasoned, don't buy it. If it looks solid, you'll understand why it's priced the way it is.

We're accountable to quality.

When the instructions are public, every kit has to hold up to a cold read. We can't ship something that only works in a controlled demo.

The community can improve on it.

Fork, adapt, submit issues. If you find a better approach to a specific behavior, we want to know. It's MIT licensed.

kumo-open-instructions is organized by kit. Each directory contains:

system-prompt.md

The main instruction file loaded into the Claude Project.

README.md

Design rationale: why we made specific choices, what the kit is not designed to do.

examples/

Sample interactions illustrating intended behavior.

CHANGELOG.md

Version history. The repo updates when the store updates.

If you've purchased a kit

The repo is the canonical source. Pull updates as they ship.

If you haven't purchased a kit

Read the instructions. Build from them freely — they're MIT licensed. The store package adds structured documentation and update notifications.

If you want to contribute

Open an issue or pull request. We review and respond.