avc init
Initialize AVC for a project. Creates .avc/ with a SQLite database, default config, and .avcignore.
avc init # initialize current directoryavc init /path/to/project # initialize a specific directoryavc init --skills claude-code # also write agent integration filesavc init --skills claude-code,cursor,windsurf| Flag | Description |
|---|---|
--skills <list> | Comma-separated agent frameworks to set up. Supported: claude-code, cursor, windsurf, generic |
--json | JSON output |
JSON output
Section titled “JSON output”{ "id": "proj-a1b2c3", "path": "/path/to/project", "name": "project", "success": true}What it creates
Section titled “What it creates”.avc/├── avc.db├── config.toml├── .gitignore└── objects/.avcignore ← in the project rootRe-running on an already-initialized project is a no-op — no data loss.
With --skills
Section titled “With --skills”For each requested framework, AVC writes the right files:
| Framework | Files written |
|---|---|
claude-code | .claude/settings.json (MCP config), .claude/skills/avc-*/SKILL.md (skill files) |
cursor | .cursor/mcp.json, .cursor/rules/avc.mdc |
windsurf | .codeium/windsurf/mcp_config.json, appends to .windsurfrules |
generic | AGENT_INSTRUCTIONS.md |
These tell the agent framework how to invoke AVC’s MCP server and when to use each tool. See Agent Integration for details.