Command Claude Code
Install agent-browser (token-efficient headless browser CLI + MCP) for 1C web UI testing.
Command Claude Code
Install agent-browser (token-efficient headless browser CLI + MCP) for 1C web UI testing.
Command Claude Code
Install Cognee MCP as the preferred persistent memory write provider and register it in the active AI client.
Command Claude Code
Install DitriX EDT-MCP into a local 1C:EDT installation and connect the active AI client.
Command Claude Code
Install Windows-MCP (desktop UI automation MCP) as a last-resort alternative to home-grown screenshot/OCR.
Command Claude Code
Download the 1C MCP server distribution from vibecoding1c.ru and install all servers from it.
Command Claude Code
Detect and optionally install the supported 1C development tools through one guided menu.
Command Claude Code
Compatibility alias for /sdlc profile names; UI testing is controlled separately by /uitests.
Command Claude Code
Dump the configuration from the infobase defined in .dev.env into the current repository files.
Command Claude Code
Rebuild the test infobase to the effective snapshot — optional DT data baseline, then the current cf + cfe sources from git.
Command Claude Code
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|gpt6) into .dev.env.
Command Claude Code
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 Claude Code
Show the status of your support tickets about MCP servers and the 1c-rules ruleset, and close a ticket you no longer need.
Command Claude Code
Closed deploy → test → fix → redeploy loop against the test infobase, until the scenarios pass or the iteration budget is exhausted.
Command Claude Code
Load current repository files into the infobase defined in .dev.env and update the DB structure.
Command Claude Code
Re-download the 1C MCP server distribution from vibecoding1c.ru, pull new images, refresh keys and restart installed servers.
Command Claude Code
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 Code
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".
Skill Claude Code
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
Skill Claude Code
Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".
Skill Claude Code
Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: