form-edit

Add form elements and event handlers from JSON definitions to 1C managed forms.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It removes the manual effort of updating existing 1C managed forms by adding new fields, commands, and event handlers from a structured description.

Core Features & Use Cases

  • Adds input fields, checkboxes, tables, pages, buttons, groups, and labels into existing forms.
  • Supports both regular forms and extension forms, including companion UI elements and event wiring.
  • Useful when you need to insert a new warehouse field, add a recalculation command, or extend a borrowed form without rewriting it.

Quick Start

Ask the form-edit skill to apply your JSON change set to the target 1C form and update its structure safely.

Frequently Asked Questions about form-edit

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

FAQPage Schema
How do I add new fields and event handlers to 1C managed forms?

To add new fields and event handlers to 1C managed forms, apply a structured JSON change set to the target form. This process safely inserts inputs, tables, pages, buttons, and commands into existing standard or extension forms without manual XML editing.

Can I use a JSON definition to modify existing 1C extension forms?

Yes, you can use a JSON definition to modify existing 1C extension forms. The tool supports both standard and extension forms, allowing you to insert new UI elements, attributes, and commands while maintaining companion elements and event validation.

Does form editing in 1C require unique ID allocation for new elements?

Yes, editing 1C managed forms requires unique ID allocation for new elements. The process allocates unique identifiers and applies support-state guardrails to ensure safe XML editing when adding inputs, tables, and buttons.

What is the best way to insert buttons and tables into a borrowed 1C form?

The best way to insert buttons, tables, and pages into a borrowed 1C form is using a structured JSON definition. This approach applies event validation and safe XML editing with support-state guardrails, extending the form without rewriting it.

Do I need lxml to automate 1C managed form editing?

Yes, you need lxml to automate 1C managed form editing. The tool depends on the lxml library to perform safe XML editing and apply structural changes from your JSON definition to the target form.

Why does adding new commands to 1C forms require event validation?

Adding new commands to 1C forms requires event validation to ensure event handlers are correctly wired to the new UI elements. This prevents runtime errors and maintains structural integrity when inserting buttons, inputs, or tables into existing managed forms.