cfe-borrow

Borrow 1C configuration objects and forms into an extension with metadata registration.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill cfe-borrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfe-borrow
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/cfe-borrow
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill cfe-borrow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Borrowing objects and forms from a 1C configuration into an extension is error-prone and complex. This Skill streamlines the process, enabling safe reuse of existing metadata while extending functionality within the extension.

Core Features & Use Cases

  • Borrow 1C configuration objects (Catalog, Document, Enum, etc.) and their forms into an extension, with proper ObjectBelonging=Adopted metadata.
  • Automatically register borrowed items in ChildObjects and support optional form borrowing with BaseForm scaffolding.
  • Auto-borrow commonly referenced resources (CommonPictures, StyleItems) when available to preserve visual consistency.

Quick Start

Run the cfe-borrow tool with -ExtensionPath and -ConfigPath to import a source object such as Catalog.Контрагенты or Catalog.Номенклатура.Form.Элемент into your extension.

Frequently Asked Questions about cfe-borrow

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

FAQPage Schema
How do I borrow 1C configuration objects into an extension?

To borrow 1C configuration objects into an extension, provide a valid source Configuration.xml and an Extension Configuration.xml. The Skill generates the required metadata and registers the borrowed items in the extension's ChildObjects.

Can I borrow forms and referenced resources from a 1C configuration automatically?

Yes, you can borrow forms and referenced resources automatically. The Skill supports automatic form borrowing with BaseForm scaffolding and auto-borrows CommonPictures and StyleItems when available to preserve visual consistency.

What do I need to set up before borrowing 1C metadata into an extension?

Before borrowing 1C metadata, you need a valid source Configuration.xml and an Extension Configuration.xml. You also need the lxml dependency installed to process and generate the required XML metadata structures.

How does borrowing 1C objects preserve visual consistency in extensions?

Borrowing 1C objects preserves visual consistency by automatically borrowing referenced resources like CommonPictures and StyleItems from the source configuration when they are available, ensuring the extension matches the original UI.

Does the 1C extension borrowing process validate inputs before generating metadata?

Yes, the 1C extension borrowing process validates inputs before generating metadata. It checks the provided source and extension Configuration.xml files to ensure safe reuse of existing metadata and prevent errors.

What is the best way to import multiple 1C configuration objects into an extension?

The best way to import multiple 1C configuration objects is using the multi-object borrowing feature. Run the tool with -ExtensionPath and -ConfigPath to generate metadata and ChildObjects registrations for all selected items simultaneously.