Chiralkit / Agent Kit

ChiralAgents

Reusable intelligence. Clearly composed.

Agent archetypes, specialist roles, and crews defined as portable contracts that humans and runtimes can share.

01 · What

An agent is a contract, not a prompt.

Each agent in the registry is a spec.json contract plus five short role files: why, what, who, how and voice. Its runtime files come from them, so the agent means the same thing in every tool.

Contract

spec.json declares the agent's input, its routes and its result states. It is the source of truth: the role files explain it and never contradict it.

Runtimes

Every agent ships adapters for Claude Code and Codex. Today ck add installs UI components; installing agents with it is next.

02 · Why

Stop copying prompts between projects.

Teams rebuild the same agent setup by hand in every repository, and every copy drifts. ChiralAgents keeps one versioned contract per agent, so a fix to the reviewer is made once, not in every copy. Every agent that produces has a mirror that verifies, so nothing ships unchecked.

Browse the agent contracts

03 · How

Roles grow on the same rings as interfaces.

A brain routes each request, routers pick the specialists, and specialists work in pairs: one builds, its mirror reviews. Every agent is built only from the rings below it, as in ChiralUI.

The six rings of ChiralAgents

The same Fibonacci rings as ChiralUI, for roles instead of interfaces: 0, 1, 1, 2, 3, 5. Each ring is built from the two before it. Foundations are the point everything starts from; at 2, chirality begins: every specialist that produces has a mirror that verifies.

See the cross-domain framing in Chiral Architecture

Open the full chirality scene

Foundations

Ring 0

The substrate every agent composes from: models, providers, tools, safety and permission policies, and the memory that travels into every session.

Brain

Ring 1a

One agent, the constant. It reads a request, classifies its domain and routes it, or says that no chain applies. In the registry: ck-brain.

Routers

Ring 1b

One router per domain, product and marketing today. Each knows its subdomain and picks the specialists that fit the task.

Specialists

Ring 2

Where chirality begins: an implementer and a critic share the same tools with mirrored functions, one produces and the other verifies, and a documenter witnesses both. In the registry: ck-frontend-build ↔ ck-frontend-review.

Personas

Ring 3

Specialists given a standing role and voice on a team, such as a product manager or an ops engineer, that people can address by name.

Crews

Ring 5

Personas and specialists working together across a project, with roles, handoffs and escalation paths. The top of the agent spiral, where agents become teammates.