# One command for 13 AI coding-assistant context files

> Source: <https://dev.to/horiamc_75e5ef599d3eba906/one-command-for-13-ai-coding-assistant-context-files-211d>
> Published: 2026-06-19 23:52:59+00:00

Every AI coding tool wants a file describing your project. Claude Code reads CLAUDE.md. Cursor reads .cursor/rules. Then there's AGENTS.md, GEMINI.md, Copilot instructions, Aider's CONVENTIONS.md, Windsurf, Cline, Continue, Kilo Code, Trae, Junie, Warp...

Same content, a dozen names and formats. Maintaining them by hand is busywork, and the second your stack changes they're stale.

```
npx @horiastanxd/claude-init
```

It analyzes the repo once - language, framework, package manager, scripts, file tree, env vars from .env.example, conventions (strict mode, linter, formatter), git info - and writes all 13 files.

No API key, no network. 100% local.

`check`

The real problem isn't generating once - it's drift. So there's a check mode:

```
npx @horiastanxd/claude-init check
```

It regenerates in memory and diffs against what's on disk, exiting non-zero on drift. Drop it in CI or a pre-commit hook:

```
- run: npx @horiastanxd/claude-init check
claude mcp add claude-init -- npx @horiastanxd/claude-init --mcp
```

Now an agent can analyze a repo and write its own context files.

`--recurse`

for monorepos (npm/pnpm workspaces)Repo: [https://github.com/horiastanxd/claude-init](https://github.com/horiastanxd/claude-init)

What tool or format should it support next?