AI-native development
Give agents structure. Keep people in control.
Last reviewed:
Cratis AI provides framework guidance for assistants building with Cratis. Direct is the control plane for agentic engineering: journeys, gates and recorded evidence help people decide how far work may progress. Neither replaces specifications, compiler checks or human review. Direct runs Cratis's own engineering; access opens in stages.
Framework guidance Generated ecosystem adapters Engineering review
Why structure matters
Faster generation should not mean faster drift.
An assistant needs more than a prompt to work within a framework. Cratis AI supplies conventions and skills; your compiler, specifications and review process check the result. Direct governs progression through journeys and gates when you use it. Guidance and gate assessments are not proof that generated code is correct.
Model before implementation
Commands, facts, streams, state views, reactions and compliance questions become explicit before an agent starts creating files.
Domain intent stays visibleBuild with the framework
Chronicle- and Arc-aware workflows know Cratis vertical slices, typed concepts, event contracts, projections, generated proxies and specification patterns.
Less plausible-but-wrong architectureUse the tools your team chose
One approved skill tree is generated into host-native layouts for Claude Code, Codex, GitHub Copilot, Cursor, OpenCode and Pi. Packaging changes; the Cratis behavior does not.
One behavior across ecosystemsOperate from durable facts
The CLI and Chronicle MCP give approved assistants documented ways to inspect events, observers and jobs without pretending a coding skill is a production credential.
Build and operations stay separateTrust by construction
Released. Ready to install. Clear about limits.
Cratis AI has a supported public release, starting with v1.0.0. Install the @cratis/pi npm package, use Cratis's own GitHub-hosted plugin marketplaces for Claude Code, Codex, GitHub Copilot and Cursor, or choose the cratis CLI's managed installation. Project context stays with the project.
Marketplace plugins track Cratis/AI's main branch, not a pinned release. The Pi package is versioned; there is no separately published, versioned package per profile. These are Cratis-hosted marketplaces, not a claim of vendor-curated central listings.
OpenCode is supported through managed installation, not a plugin marketplace entry. Kiro, Junie and Gemini are not supported. Installation does not replace compiler gates, specifications, CI or human review.
Spec-driven development
Intent that can be checked.
See spec-driven development with event models and specs for the path from intent through specifications to code, and the limits of each step.