interface-edit

Adjust 1C CommandInterface.xml to hide, show, place, and reorder UI elements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The interface-edit skill solves the problem of having to manually edit 1C CommandInterface.xml to show, hide, group, and reorder commands, which is error-prone and time-consuming.

Core Features & Use Cases

  • Show/Hide specific commands by setting CommandsVisibility entries (including skipping redundant changes).
  • Place commands into groups via CommandsPlacement (with automatic CommandInterface section creation if missing).
  • Control ordering for both command groups and subsystems using CommandsOrder, SubsystemsOrder, and GroupsOrder.
  • Use inline parameters or batch JSON to apply multiple operations in one run, then optionally auto-validate the result.

Quick Start

Use interface-edit to update Subsystems/Продажи/Ext/CommandInterface.xml by hiding the command Catalog.Товары.StandardCommand.OpenList.

Frequently Asked Questions about interface-edit

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

FAQPage Schema
How do I hide or show commands in 1C CommandInterface.xml without manual editing?

To hide or show commands in 1C CommandInterface.xml without manual XML editing, use the interface-edit skill to set CommandsVisibility entries, automatically skipping redundant changes to ensure consistent UI behavior across configuration variants.

Can I batch reorder multiple 1C subsystem and command UI elements at once?

Yes, you can batch reorder 1C subsystem and command UI elements using a DefinitionFile JSON, applying multiple CommandsOrder, SubsystemsOrder, and GroupsOrder operations in a single run to mass adjust the configuration.

What is the best way to place 1C commands into groups via XML configuration?

The best way to place 1C commands into groups via XML configuration is using the CommandsPlacement operation, which automatically creates the CommandInterface section if it is missing during the placement process.

Does the interface-edit tool validate 1C configuration changes automatically?

Yes, the interface-edit tool validates 1C configuration changes automatically through an auto-validate trigger that runs after applying show, hide, place, and reorder operations to the CommandInterface.xml file.

Do I need to manually create the CommandInterface section before placing 1C commands?

No, you do not need to manually create the CommandInterface section before placing 1C commands; the tool supports a CreateIfMissing behavior that automatically generates the required section during CommandsPlacement operations.