subsystem-compile

Generates 1C:Enterprise subsystem XML sources from a JSON definition.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill subsystem-compile-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subsystem-compile
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/subsystem-compile
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill subsystem-compile-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually authoring 1C:Enterprise subsystem metadata requires writing verbose XML files, building the correct directory structure, and registering the object in Configuration.xml or a parent subsystem. This Skill automates that entire process from a compact JSON definition. ## Core Features & Use Cases - JSON-to-XML compilation: Converts a JSON subsystem definition (name, synonym, content, picture, command interface flags) into valid 1C XML sources and file structure. - Automatic parent registration: Registers the new subsystem in Configuration.xml or nests it under an existing parent subsystem XML. - Built-in validation and safety: Runs mandatory 8.3.27 correctness validation before committing, supports dry-run mode by default, and enforces vendor support guards for locked objects. - Use Case: You need to add a "Sales" section containing catalogs and reports to your configuration. Provide a JSON definition with the name and content list, and the Skill generates the XML, folder structure, and registration in one MCP call. ## Quick Start Ask the assistant to create a 1C subsystem named "Продажи" containing Catalog.Номенклатура in your configuration source directory using the subsystem-compile skill.

Frequently Asked Questions about subsystem-compile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a 1C subsystem from JSON?▼

Call the unica.subsystem.compile MCP tool with a JSON definition containing at least the subsystem name, plus the OutputDir pointing to your configuration source root. The tool generates the XML files, folder structure, and registers the subsystem in Configuration.xml automatically.

How to add a nested subsystem in 1C configuration sources?▼

Pass the Parent parameter with the path to the parent subsystem's XML file, for example config/Subsystems/Продажи.xml, along with your JSON definition. The new subsystem is generated and registered as a child of that parent.

What fields are required in the subsystem JSON definition?▼

Only the name field is mandatory. Optional fields include synonym, comment, includeInCommandInterface, useOneCommand, explanation, picture, and content listing objects like Catalog.Товары or Document.Заказ.

Does subsystem-compile validate the generated 1C XML?▼

Yes, mandatory correctness validation against platform version 8.3.27 runs before any changes are committed. The NoValidate parameter only hides the detailed auto-validation report; it does not disable the required check.

Can I preview changes before modifying configuration files?▼

Yes, the tool runs in dry-run mode by default. Pass dryRun: false only when you explicitly want the mutation applied, which protects your configuration sources from unintended changes.

What happens if the subsystem object is locked by vendor support?▼

A vendor support guard inside the unica MCP tool blocks edits to locked or read-only supported objects. In that case, use a CFE extension or an explicit support-state change plan instead of editing raw support metadata.