agent-atlas-studio: Instructions file for Claude Code

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What this is

agent-atlas-studio is an Erwin-style visual modeler for agentic AI systems. You lay out a whole platform — orchestrator, tasks, agents, MCP tools, jobs, routers, and systems (datastores) — as one unified, collapsible graph, validate each object live against the agent-atlas JSON schema, and export a versioned registry of YAML manifests.

It runs identically as a static web build (GitHub Pages) and a local-first Tauri 2 desktop app. No backend, no auth, no cloud dependency.

Commands

npm install                 # requires submodule: git submodule update --init
npm run dev                 # web dev server → http://localhost:5173
npm run build               # static build → dist/
npm run preview             # serve the production build
npm run lint                # eslint .
npm run tauri dev           # desktop app (runs `npm run dev` first, loads localhost:5173)
npm run tauri build         # package the desktop app (runs `npm run build` first)

There is no test runner configured. npm run lint (ESLint flat config in eslint.config.js) is the only automated check.

The GitHub Pages build sets BASE_PATH=/agent-atlas-studio/ so assets resolve on the project-pages subpath; dev and the Tauri build use base: '/' (see vite.config.js).

The submodule is the source of truth — do not duplicate the schema

vendor/agent-atlas is a git submodule (Fox-River-AI/agent-atlas) holding the canonical manifest schema and deterministic validators. The point of vendoring it is that there is exactly one copy of the spec, so the UI can never drift from it.

• src/atlas/schema.js imports schemas and compiles Ajv validators. The tool schema is imported straight from the submodule (vendor/agent-atlas/registry/schema/tool.schema.json). The agent, job, system, router, and orchestrator schemas live in src/atlas/schemas/*.json — these are prototyped in-studio for fast iteration and meant to be upstreamed to agent-atlas once proven. When changing object shapes, edit the studio schema, but treat the submodule tool schema as canonical.
• Schemas declare JSON Schema draft 2020-12, so schema.js imports ajv/dist/2020 (the default Ajv export only knows draft-07 and will throw at compile()).
• The registry export (src/atlas/model.js) is built to satisfy agent-atlas's own governance/ci/validate_registry.py, so the same checks that gate the OSS repo gate what this UI produces.