1c-form-edit

Modify 1C Form.xml by adding elements, attributes, and commands.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill 1c-form-edit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-form-edit
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/skills/1c-form-edit
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill 1c-form-edit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Editing Form.xml in 1C projects can be error-prone and time-consuming when adding UI elements, data attributes, or commands to an existing form. This skill streamlines the process by providing deterministic insertion, ID allocation, and generation of necessary event handlers and companions.

Core Features & Use Cases

  • Automatically allocates IDs from the correct pools for new form elements, attributes, and commands.
  • Generates companion elements (ContextMenu, ExtendedTooltip, etc.) and event handlers to ensure consistent behavior.
  • Use Case: modify an existing Form.xml to add a new input field and associated logic without breaking layout or IDs.

Quick Start

Install the skill and run 1c-form-edit with a target Form.xml path and a JSON spec describing additions

Frequently Asked Questions about 1c-form-edit

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

FAQPage Schema
How do I add a new input field to 1C Form.xml without breaking existing IDs?

To add input fields to 1C Form.xml safely, this skill automates deterministic element placement and allocates new IDs from the correct pools, ensuring added input fields do not conflict with existing structures.

How does 1C form modification handle event handler wiring and companion elements?

1C form modification through this skill automatically generates companion elements like ContextMenu and ExtendedTooltip, while wiring event handlers to ensure consistent UI behavior during Form.xml changes.

What is the best way to automate adding attributes and commands to existing 1C forms?

The best way to automate adding attributes and commands to existing 1C forms is using a JSON spec that defines additions, allowing deterministic insertion into Form.xml structures across projects.

Can I use this 1c-form-edit skill to modify Form.xml structures across multiple 1C projects?

Yes, you can use this skill to modify Form.xml structures across multiple 1C projects by applying deterministic insertion rules and automatic ID allocation to each target form.

What format do I need to provide to automate 1C form modification?

You need to provide a target Form.xml path and a JSON spec describing additions to automate 1C form modification, enabling the skill to allocate IDs and generate companion elements.