antoumpas

Ajolote AI — AI skill for Claude Code

AI community

Shared AI agent configuration for multi-tool teams.

How to install Ajolote AI

This entry records only its repository, not the path inside it, so there is no exact command to give. Open antoumpas/ajolote-ai and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Ajolote AI does

Shared AI agent configuration for multi-tool teams. ajolote keeps a single canonical config (.agents/config.json) and translates it into the native format of each developer's AI coding assistant — Claude Code, Cursor, Windsurf, GitHub Copilot, Cline, and Aider. Tool-specific files are gitignored; only the shared config is committed.

Alternatives in AI

  • Part 4 — Generate AGENTS.md And AI Agent Configuration Files — I'll help you create the instruction files that will guide your AI coding assistant to build your MVP 2.1k ★
  • Paca — AI-native, free, open-source alternative to Jira, Trello, ClickUp & Monday 1.8k ★
  • Wax — Shared Single-file memory layer for all your agents, sub mili-second RAG over text, photo and video on Apple S 791 ★

README

ajolote

One shared AI agent config for teams where developers use different tools.

You commit `.agents/` — a single directory of rules, skills, personas, and MCP server definitions. Every developer runs `ajolote use ` and gets a freshly generated config in their tool's native format. No more per-tool config files committed to git, no more "it works on my Cursor but not your Claude Code."

Works with any language or framework. Supports Claude Code, Cursor, Windsurf, GitHub Copilot, Cline / Roo Code, Aider, Gemini CLI, and Codex CLI. Also generates a committed `AGENTS.md` (Linux Foundation / AAIF standard) that any compatible tool can read without ajolote installed.

**When it helps most:**

  • Your team uses different tools (Alice is on Claude Code, Bob is on Cursor, CI runs Copilot)
  • You want a single place to evolve agent rules without touching per-tool config files
  • You need MCP servers shared across tools, with personal tokens staying local and out of git
  • You want ajolote diff in CI to catch config drift before it reaches main

The mental model

Committed to git ✅ Gitignored — generated locally ❌
.agents/config.json — the canonical config CLAUDE.md, .claude/settings.json
.agents/rules/*.md — your ground rules .cursor/rules/agents.mdc, .cursor/mcp.json
.agents/skills/*.md — reusable instructions .windsurf/rules/agents.md
.agents/personas/*.md — role behaviours .github/copilot-instructions.md
.agents/context/*.md — project knowledge .clinerules, .roo/mcp.json, .roomodes
.agents/commands/*.md — shared slash commands .aider.conf.yml, GEMINI.md
AGENTS.md — AAIF standard (any tool reads it) .codex/config.toml

Everyone edits the `.agents/` files. Each developer runs `ajolote use ` once to generate their own tool config from the shared source of truth.

Install

**macOS / Linux**

curl -fsSL https://raw.githubusercontent.com/antoumpas/aj