subsystem-compile

Compile 1C subsystem JSON definitions into XML metadata and directory structures.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill subsystem-compile-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subsystem-compile
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/subsystem-compile
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill subsystem-compile-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone work of creating 1C subsystem XML artifacts and wiring them into the proper parent configuration, by compiling a structured JSON definition into the required filesystem structure and metadata registration.

Core Features & Use Cases

  • Subsystem XML generation from JSON: Converts a JSON definition (minimum field name) into a valid 1C subsystem MetaDataObject XML file.
  • Filesystem structure & child stubs: Creates the Subsystems directory, writes the subsystem XML, and optionally generates stub XML files for child subsystems.
  • Parent registration (Configuration.xml or nested parent): Inserts a new Subsystem reference into the correct parent’s ChildObjects section and avoids duplicate registration.
  • Character-set safe execution: Supports Base64 variants of path and JSON inputs to prevent Cyrillic marshalling issues in Windows PowerShell.

Use case example: When you need to add a new subsystem like “Продажи” with predefined Content objects (e.g., catalogs/documents) and possibly nested child subsystems, you provide the JSON definition and an output directory, and the Skill generates the XML artifacts and updates Configuration.xml so it becomes part of the build.

Quick Start

Create a new subsystem by running subsystem-compile with an inline JSON definition and an OutputDir pointing to your 1C configuration root.

Frequently Asked Questions about subsystem-compile

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

FAQPage Schema
How do I generate 1C subsystem XML metadata from a JSON definition?

To generate 1C subsystem XML metadata, you compile a JSON definition into the required filesystem structure. The process creates the Subsystems directory, writes the subsystem XML file, and registers the reference into Configuration.xml.

Can I add nested child subsystems and content objects when generating 1C configuration files?

Yes, you can add nested child subsystems and content objects. The JSON definition supports defining content objects like catalogs or documents and optionally generates stub XML files for child subsystems during compilation.

What is the best way to register a new 1C subsystem into Configuration.xml without duplicates?

The best way to register a 1C subsystem without duplicates is to compile the JSON definition, which automatically inserts a new Subsystem reference into the parent's ChildObjects section while avoiding duplicate registration.

How do I handle Cyrillic characters in paths when generating 1C subsystem XML in Windows PowerShell?

To handle Cyrillic characters safely in Windows PowerShell, use Base64 variants for path and JSON inputs. This prevents marshalling issues when executing the 1C subsystem compilation.

Does 1C subsystem generation require a parent XML file or can it update the main Configuration.xml?

1C subsystem generation can update either the main Configuration.xml or a provided parent XML file. The compiler inserts the subsystem reference into the correct parent's ChildObjects section.

What is the minimum JSON input needed to create a 1C subsystem?

The minimum JSON input needed to create a 1C subsystem is the mandatory 'name' field. This allows the compiler to generate the basic subsystem MetaDataObject XML file and directory structure.