Rules\skills\subagens for vibecoding in 1C(bsl)
This repository also configures its own agents. See what ai_rules_1c tells them →
Skill Claude Code
Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".
Skill Claude Code
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Also use when the user says "openspec update change" or "opsx update". If the user…
Skill Claude Code
A handoff process for making changes to 1C systems through a human rather than directly editing source files. It uses a Configurator package or a reviewable difference, especially when the system is vendor-locked, binary, or available only through MCP.
Skill Claude Code
Create, maintain and run reusable tests of 1C business logic using the project's verified framework or runner. Optional: the model chooses when persistent regression coverage adds value beyond a focused result check.
Skill Claude Code
Create or maintain reusable UI regression tests for a 1C web client, runnable without an AI agent. Optional: choose when repeatable coverage is useful; ordinary interactive UI checks remain with 1c-tester.
Skill Claude Code
UI checks in the 1C thin client through QA MCP (1c-qa, qa / ui): session, observe → act → assert, platform behaviour, unknown outcomes, journal and verdicts. Main UI route when connected and TOOLQA allows it; the web client is the fallback.
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: