subsystem-compile

Generate 1C subsystem XML from a JSON definition.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill subsystem-compile-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subsystem-compile
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/subsystem-compile
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill subsystem-compile-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

This Skill turns a JSON definition into a ready-to-use 1C subsystem file set, eliminating manual XML editing and registration errors when building configuration structures.

Core Features & Use Cases

  • Subsystem generation: Creates the subsystem XML from a concise JSON payload.
  • Nested structure support: Builds child subsystem stubs and registers them in the parent hierarchy.
  • Configuration-safe workflow: Detects configuration format version, normalizes content references, and validates output for repeatable use.
  • Use case: Use it when you need to add a new functional section such as Sales, HR, or Reports into a 1C configuration without hand-editing metadata files.

Quick Start

Ask the skill to compile a 1C subsystem from your JSON definition into the target configuration directory.

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 from a JSON definition?

To generate 1C subsystem XML from a JSON definition, provide a concise JSON payload specifying the structure, and the scripts will create the corresponding XML files for configuration exports and command interface setup.

Can I create nested child subsystems in 1C from JSON?

Yes, you can create nested child subsystems from JSON. The process builds child subsystem stubs and registers them within the parent hierarchy for accurate 1C configuration metadata.

Does generating 1C configuration subsystems require PowerShell and Python?

Generating 1C configuration subsystems relies on resilient PowerShell and Python scripts to handle XML generation, format-version detection, and validation, requiring the lxml dependency for processing.

How do I add a new functional section to a 1C configuration without manual XML editing?

You can add a new functional section to a 1C configuration by defining it in a JSON payload. The scripts compile this into ready-to-use subsystem XML, eliminating manual metadata file editing and registration errors.

What is the best way to validate 1C subsystem XML generation and format versions?

The best way to validate 1C subsystem XML generation is using the built-in validation scripts. They detect the configuration format version, normalize content references, and ensure output accuracy for repeatable use.

Are there limitations when scaffolding child subsystem stubs for 1C configurations?

When scaffolding child subsystem stubs for 1C configurations, the process focuses on generating structural XML and parent registration. It does not replace full business logic implementation within the 1C platform itself.