1c-forms

Analyze, validate, and compile 1C managed form Form.xml files via PowerShell scripts.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-forms-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-forms
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/1c-forms
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-forms-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Working with 1C managed forms means dealing with Form.xml files that can span tens of thousands of lines, making manual inspection, structural validation, and safe editing slow and error-prone. This Skill provides a governed toolkit for analyzing form dumps, checking structural correctness, and compiling or patching Form.xml only under an explicit assisted artifact mode. ## Core Features & Use Cases - Form analysis (info): Reads an exported Form.xml and outputs a compact summary of the element tree, attributes, commands, and events, replacing thousands of XML lines with 50-100 lines of context. - Structural validation (validate): Checks ID uniqueness, companion elements, DataPath references, command bindings, and event handlers, returning a pass/fail report after Configurator export. - Design patterns reference (patterns): Provides form archetypes (document, list, catalog, wizard), naming conventions, and layout principles for designing forms in Configurator or BSL. - Compile and edit (assisted mode only): Builds Form.xml from a JSON DSL or applies JSON patches to an existing form, always followed by validation; raw orchestrator writes to Form.xml are forbidden. - Use Case: After changing a document form in the 1C Configurator and exporting to src/, run the validate sub-skill to confirm structural integrity, then use info to review the resulting element tree before committing. ## Quick Start Ask the assistant to run the 1c-forms validate sub-skill on your exported Form.xml file to check it for structural errors.

Frequently Asked Questions about 1c-forms

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

FAQPage Schema
How do I validate a 1C managed form Form.xml file?

Run the form-validate.ps1 script with the -FormPath parameter pointing to your exported Form.xml. It checks ID uniqueness, companion elements, DataPath references, and command bindings, returning exit code 0 when all checks pass.

How can I view the structure of a large 1C form without reading all the XML?

Use the form-info.ps1 script, which condenses an exported Form.xml into a compact tree of elements, attributes, commands, and events. Output is limited to 150 lines by default with -Offset pagination for larger forms.

Can I generate or edit Form.xml directly with this skill?

Only when the proposal's artifact_mode is set to assisted. The compile sub-skill builds Form.xml from a JSON DSL and edit applies JSON patches, both followed by validation; raw writes by the orchestrator are always forbidden.

What PowerShell version is required for the 1C form scripts?

The scripts require Windows PowerShell 5.1, the version built into Windows. They are invoked with powershell.exe -NoProfile and are not designed for PowerShell Core or other shells.

What operations are forbidden when working with 1C forms in this skill?

Forbidden operations include form-add, template-add, mutating an object's ChildObjects, using -FromObject generation, borrowing forms, and any raw Write or StrReplace of Form.xml outside the compile/edit scripts.

When should I use Configurator instead of the compile script for 1C forms?

Use Configurator when artifact_mode is manual (the default) or when the target form does not yet exist in metadata. The compile script only writes Form.xml for forms already present in the configuration.