Claudenv

claudenv

[](https://www.npmjs.com/package/claudenv)

Set up [Claude Code](https://docs.anthropic.com/en/docs/claude-code) in any project with one command. claudenv analyzes your codebase and generates everything Claude needs to work effectively — documentation, rules, hooks, MCP servers, slash commands, **cross-session memory, and a self-extending harness that equips Claude with new skills on demand (1.3.2).**

**New in 1.3.2 — self-extending harness.** Claude can now introspect what claudenv gives it (`claudenv capabilities`), find what's missing for the task, and equip it from the [awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills) registry (`claudenv skills search|add`) — plus first-class **kimi-webbridge** browser automation. New `/harness` command + skill drive it autonomously. See [CHANGELOG.md](./CHANGELOG.md).

**1.3.0** — split memory layout, `vibe-decisions` skill, CLI: `memory`, `decisions`, `canon`, `doctor`. Companion Python package `claudenv-memory` on PyPI (alpha).

Quick Start

npm i -g claudenv && claudenv

Open Claude Code in any project and type `/claudenv`. That's it.

What happens when you run `/claudenv`

Claude reads your code, asks a few questions, and generates:

• CLAUDE.md — project overview, architecture, key commands
• Rules — coding style, testing patterns, workflow guidelines (.claude/rules/)
• MCP servers — auto-detected from your stack, configured in .mcp.json
• Slash commands — /init-docs, /update-docs, /validate-docs, /setup-mcp, /improve, /deeper, /why, /decisions, /canon, /just-code (1.3.0)
• Hooks — validation on tool use, audit logging, decisions-logger (PostToolUse Write), regen-index (SessionEnd) — .claude/settings.json

Everything is committed to your repo. Team members get the same Claude experience.

Autonomous Loop

The killer feature. `claudenv loop` runs