1c-rules: rules and skills for 1C development

Install

claude plugin marketplace add comol/ai_rules_1c
claude plugin install 1c-rules@1c-rules

This is third-party code. Review the repository files before installing.

What it does

1c-rules installs a unified AGENTS.md rule set into a 1C project, along with on-demand instructions for BSL, forms, data composition schemas, registers and queries, 13 specialized subagents and slash commands. The main 1c-metadata-manage skill changes configuration metadata through typed, validated operations instead of hand-editing XML. The rules are designed for a 1C MCP server bundle: metadata graph, code search, BSL syntax checking, platform help, SSL and templates. The installer detects active agents and adapts files for each.

Who it is for. 1C developers who write code and modify configurations with AI agents.

Example request

Add a Manager attribute of type CatalogRef.Users to the SalesOfGoods document and show it on the document form

Limitations

The main installer and most tools are PowerShell; only five commands have Python ports. Full functionality requires the MCP server bundle from vibecoding1c.ru running in Docker. The 1c-code-check-mcp server uses the commercial 1C:Naparnik service.

How to disable. Run install.ps1 remove for a tool or install.ps1 eject; in Claude Code remove the 1c-rules plugin via /plugin.

Security check

• The installer and skills run PowerShell and Python scripts
• Tools change configuration metadata and operate on infobases
• Can connect MCP servers and external services, including 1C:Naparnik and the Gemini API for transcription

README in short

1c-rules is a portable set of rules, subagent roles, on-demand instructions and integrations for 1C:Enterprise 8 development with AI agents. It installs via the plugin marketplaces of Cursor, Claude Code, Codex and OpenCode, by the agent itself via AGENT-INSTALL.md, or with the install.ps1 PowerShell script. The README details the catalog of rules, subagents, skills and 1C ecosystem MCP servers. It also sets up an OpenSpec workspace for spec-driven work.

SKILL.md

---
name: 1c-metadata-manage
description: "1C metadata management — create, edit, validate, and remove configuration objects (catalogs, documents, registers, enums), managed forms, data composition schemas (SKD), spreadsheet layouts (MXL), roles, external processors (EPF/ERF), extensions (CFE), configurations (CF), databases, subsystems, command interfaces, templates. Use when working with 1C metadata structure."
---

# 1C Metadata Manage — Skill Dispatch

Use this skill when the task involves **1C metadata structure** (creating, editing, validating, or removing configuration objects, forms, reports, layouts, roles, extensions, or databases).

## Hard rule

- **Unambiguous one-line fix** of an existing value that cannot break structure — a synonym / comment typo, a boolean flag flip on an existing element. Anything that adds / removes / reorders elements, touches UUIDs, or spans more than one line of XML is not "one-line".
- **Skill not available in the session** (files not installed / not exposed) — state it once in one line, then hand-edit with `metadata-xml-workarounds.md` loaded and validate per `verification-gates.md`.
- **Read-only analysis** of metadata XML is not a mutation — reading files directly is fine (subject to `mcp-first-search.md` for locating them).

## Vendor support gate

Every mutating tool refuses to edit a locked ("на замке") object of a typical configuration on vendor support and refuses to delete one still on support — the run exits `1`, the refusal is the correct outcome (extension first, `support-edit` only as a stated decision): [support-manage.md](docs/support-manage.md).

## Path conventions

PowerShell examples in this skill (`SKILL.md` and every `docs/*.md`) use the prefix `skills/1c-metadata-manage/tools/...`. That prefix is **relative to the active tool's skills directory**, not to the repository root:

- After installation: the script lives under `<tool>/skills/1c-metadata-manage/tools/...` (e.g. `.cursor/skills/1c-metadata-manage/tools/...`, `.claude/skills/1c-metadata-manage/tools/...`, `.kilo/skills/1c-metadata-manage/tools/...`, `.ai-agent/skills/1c-metadata-manage/tools/...`). Active tools that load this skill resolve the prefix automatically.
- In the `1c-rules` source repository (when editing the skill itself): the same script lives under `content/skills/1c-metadata-manage/tools/...`. Prepend `content/` when running the example outside of an installed project.

Related