Enterprise Agent Teams in minutes, not sprints.Visual design for humans. Deterministic `.claude` files for machines.

Cut prompt drift, onboarding friction, and compliance guesswork. Model agents, skills, policies, and settings in Canvas, enforce relationship rules with the build gate, and export repo-ready files.

Try Demo Create from Template Open Canvas Read Docs API Reference

Team Delivery Signals

Concrete outcomes for onboarding, standardization, and release confidence.

Starter teams8 templatesExportOne-click .claude bundleValidationBuild gate + auto-fix

Problems This Solves

- Prompt sprawl from duplicated instructions across agents
- Assumptions that drift when policy context is not linked
- Broken `.claude` exports caused by invalid relationships
- Audit gaps when prompts are assembled manually

Pick a Starting Path

Build from scratch
Start a new team design in Canvas and model behavior directly.
Open Interactive Demo
Standardize team setup
Start from a template and adapt it to your codebase workflow.
Create from Template
Run governance checks
Validate structure and export files that are reviewable and diffable.
Read Validation Flow

How It Works

1. Define the exact `.claude/` output your repository should contain.
2. Use Canvas to visualize agents, skills, policies, and valid relationships.
3. Run the build gate to enforce schema and Claude compliance.
4. Preview and download the export bundle.
5. Commit generated files and run Claude Code against versioned context.

Starter Agent Teams

Open an instantiated team directly from here, then tailor behavior and policies for your project.

8 templates not instantiated yet. Create them from /packs/new.

What You Add to Your Repo

project-root/
  .claude/
    agents/
      <agent>.md
    skills/
      <skill>/SKILL.md
    rules/
      <policy>.md
    settings.json
  .mcp.json
  CLAUDE.md

Why Teams Keep This in CI

- Canvas makes team behavior reviewable before any file is exported.
- Shared skills and policies cut repeated prompt setup across repos.
- Deterministic exports keep runtime behavior diffable across environments.
- Build gate checks reduce broken exports and audit surprises.

Feedback and Product Updates

Send feedback or sign up for release updates.