Vendor Neutral

VERSA 1.0
One .ai/ folder,
every runtime

The portable repo spec for agentic coding. Capture rules, prompts, agents, and more—ship to any IDE, CLI, or hosted copilot.

8
Canonical primitives
5
npm packages released
230
Tests passing
70
Conformance scenarios
.ai/
.ai/
├── context.json          # Base configuration
├── profiles/
│   ├── cursor.json       # Cursor IDE settings
│   ├── windsurf.json     # Windsurf overrides
│   └── claude.json       # Claude-specific
├── rules/
│   ├── style.md          # Code style guide
│   └── security.md       # Security policies
├── agents/
│   └── code-reviewer.json
└── tools/
    └── mcp-servers.json
Why VERSA

Interoperable from day one

Everything you need to hand consistent project context to modern agents, built with AAA accessibility and security best practices.

Portable by design

One `.ai/` folder that every agent runtime can parse. Structured merge rules keep overrides predictable across tools.

Security-first

Explicit deny → ask → allow permissions, secret bindings, and knowledge redaction baked into the spec from day one.

Developer experience

Lintable, diffable, testable. Designed for CI/CD pipelines while staying approachable for humans to author.

Eight Canonical Categories

Everything an agent needs to understand your repo

VERSA balances machine readability with human-friendly authoring. Markdown gets JSON front matter, JSON gets deeply merged.

Rules

Persistent project context delivered to every agent call.

Prompts

Reusable templates with typed variables and inline tests.

Agents

Declarative presets describing goals, tools, context attachments.

Memory

Retention policies and durable notes – session, project, or none.

Knowledge

Ingestion config for docs, repos, URLs with redaction directives.

Tools

MCP servers and HTTP descriptors for reproducible capabilities.

Settings

Model routing, budgets, UI preferences, and profile overlays.

Permissions

Policy enforcement with secret bindings and ask-before-run prompts.

Workflow

From authoring to runtime in four steps

Designed for DX: lintable, diffable, and easy to automate in CI while staying approachable for humans.

1

Author

Capture durable guidance in Markdown with `ai:meta` preambles for scope, priority, and attach mode.

2

Validate

Run `versa lint` to check JSON Schemas and Markdown metadata across environments.

3

Launch

Start MCP servers, merge profile overlays, hand the same `.ai/` context to all tools.

4

Evolve

Ship conformance scenarios, design updates, and spec proposals via issues.

Ecosystem

The dotAIslash ecosystem

All 8 repositories: specs, schemas, CLI tooling, examples, adapters, conformance suites, website, and community.

dotaislash-spec

Spec

Canonical VERSA 1.0 specification and design rationale.

Open repository

dotaislash-schemas

v1.0.0

JSON Schema validation for `.ai/` files - v1.0.0 released.

Open repository

dotaislash-cli

v1.0.0

Reference CLI tool (versa init, lint, context) - v1.0.0 released.

Open repository

dotaislash-examples

v1.0.0

10 validated example configurations for various project types.

Open repository

dotaislash-adapters

v1.0.0

Transform VERSA to native tool formats (Cursor, Windsurf) - v1.0.0.

Open repository

dotaislash-conformance

v1.0.0

70 black-box scenarios to certify VERSA-compatible runtimes.

Open repository

dotaislash.github.io

Website

Landing site and documentation built with Next.js 15 + Tailwind 4.

Open repository

.github

Org

Organization profile and community documentation.

Open repository

Ready to wire your repo for every agent?

Clone the examples, lint your .ai/ folder, and open a spec issue if you need new capabilities. We're building VERSA openly with the community.