initproject
25Command
Initialize a 1C project — test infobase from an existing IB / .cf / .dt, full source dump (cf + all cfe) into a git repository, first commit.
Command
Initialize a 1C project — test infobase from an existing IB / .cf / .dt, full source dump (cf + all cfe) into a git repository, first commit.
Command
Install agent-browser (token-efficient headless browser CLI + MCP) for 1C web UI testing.
Command
Install Cognee MCP as optional persistent agent memory and register it in the active AI client.
Command
Install DitriX EDT-MCP into a local 1C:EDT installation and connect the active AI client.
Command
Install Windows-MCP (desktop UI automation MCP) as a last-resort alternative to home-grown screenshot/OCR.
Command
Download the 1C MCP server distribution from vibecoding1c.ru and install all servers from it, in the stable or the beta image channel.
Command
Detect and optionally install the supported 1C development tools through one guided menu.
Command
Toggle lightweight QA mode — set VERIFICATIONDEPTH (full|standard|lite) in .dev.env and, at level lite, disable UI testing (UITESTING=off).
Command
Dump the configuration from the infobase defined in .dev.env into the current repository files.
Command
Rebuild the test infobase to the effective snapshot — optional DT data baseline, then the current cf + cfe sources from git.
Command
Adapt the ruleset to the model that is actually running — normalize a free-form model name to a profile slug and write AGENTMODEL (opus5|sonnet5|fable5|gpt56) into .dev.env.
Command
Send a problem report about a 1C MCP server or about the 1c-rules ruleset to the support service (Yandex Cloud Function -> Yandex Database).
Command
Show the status of your support tickets about MCP servers and the 1c-rules ruleset, and close a ticket you no longer need.
Command
Closed deploy → test → fix → redeploy loop against the test infobase, until the scenarios pass or the iteration budget is exhausted.
Command
Load current repository files into the infobase defined in .dev.env and update the DB structure.
Command
Re-download the 1C MCP server distribution from vibecoding1c.ru, pull new images, refresh keys, restart installed servers, and switch the image channel between stable and beta.
Command
Update the 1c-rules ruleset from GitHub (https://github.com/comol/airules1c).
Command Claude Code
Implement tasks from an OpenSpec change (Experimental).
Command Claude Code
Archive a completed change in the experimental workflow.
Command Claude Code
Enter explore mode - think through ideas, investigate problems, clarify requirements.
Command Claude Code
Propose a new change - create it and generate all artifacts in one step.
Skill Claude CodeCodex
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Skill Claude CodeCodex
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Skill Claude CodeCodex
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.