subsystem-expert

Manage 1C:Enterprise subsystem metadata and CommandInterface.xml via JSON-driven operations.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill subsystem-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subsystem-expert
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/subsystem-expert
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill subsystem-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of managing 1C:Enterprise 8.3 subsystem metadata and its CommandInterface.xml without manually editing XML in multiple places.

Core Features & Use Cases

  • Subsystem creation (compile): builds the subsystem metadata XML from a JSON definition, creates the required folder/file structure, and registers it in the parent Configuration.xml (or nested parent).
  • Subsystem editing (edit): performs targeted updates to an existing subsystem’s composition (content and child objects) and changes key properties from JSON-driven operations.
  • Command interface editing (interface-edit): updates CommandInterface.xml visibility, placement, and ordering for commands, groups, and subsystems using deterministic operations.
  • Recommended orchestration: use it for subsystem operations, while using separate skills for analysis (inspect) and validation (validate).

Quick Start

Call /subsystem-expert compile with a JSON subsystem definition to generate the subsystem XML and register it into the target configuration output directory.

Frequently Asked Questions about subsystem-expert

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

FAQPage Schema
How do I generate 1C:Enterprise subsystem metadata without manually editing XML?

To generate 1C subsystem metadata without manual XML editing, use a JSON-driven compile operation that builds the subsystem XML, creates the required folder structure, and registers it in the parent Configuration.xml.

What is the best way to update CommandInterface.xml visibility and ordering in 1C?

The best way to update CommandInterface.xml visibility and ordering is through deterministic interface-edit operations that adjust command, group, and subsystem placement using JSON-driven inputs.

How does JSON-driven subsystem editing work for 1C configuration development?

JSON-driven subsystem editing works by applying targeted updates to an existing 1C subsystem's composition, modifying content, child objects, and key properties directly from the JSON definition.

Do I need PowerShell to manage 1C subsystem metadata automation?

Yes, managing 1C subsystem metadata automation requires deterministic PowerShell script execution to apply compile, edit, and interface-edit operations during configuration development workflows.

Can I validate 1C subsystems after generating the metadata XML?

Yes, you can validate 1C subsystems after generation by running optional auto-validation via the corresponding validate scripts to ensure metadata integrity.

When should I use separate skills instead of subsystem-expert for 1C configuration tasks?

You should use separate skills for analysis and validation tasks, while restricting subsystem-expert to subsystem creation, composition editing, and command interface visibility adjustments.