cfe-borrow

Borrow 1С:Enterprise metadata objects into a CFE extension as adopted XML.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of manually recreating 1С:Enterprise 8.3 metadata in an extension when you only need to reuse (adopt) existing objects—especially forms—without breaking extension structure.

Core Features & Use Cases

  • Borrow base 1C metadata into a CFE extension: creates XML metadata with ObjectBelonging=Adopted and registers borrowed objects in the extension’s ChildObjects.
  • Borrow forms and optionally bind them to object data paths: can generate a managed extension form shell for a specific object’s form.
  • Add new fields to a borrowed form with correct data bindings: with -BorrowMainAttribute, the form’s DataPath bindings are preserved so follow-up steps like /meta-edit and /form-edit can place new requisites onto the form.
  • Handles multiple objects in one run: supports batching via -Object with ;; separators.
  • Verification workflow: provides /cfe-validate to validate the resulting extension.

Quick Start

Run the cfe-borrow skill to adopt Catalog.Контрагенты from your base Configuration.xml into your extension at src, and then validate the extension.

Frequently Asked Questions about cfe-borrow

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

FAQPage Schema
How do I safely borrow 1C metadata objects into a CFE extension?

Borrowing 1C metadata into a CFE extension automates generating Adopted XML metadata and registering objects in ChildObjects. This safely reuses base configuration objects without manually recreating them or breaking the extension structure.

How do I add new requisites to borrowed managed forms in 1C extensions?

To add new requisites to borrowed managed forms, use the -BorrowMainAttribute flag to preserve form DataPath bindings. This ensures follow-up form edits correctly place new fields with accurate data bindings.

Does the cfe-borrow skill support validating the generated extension XML?

Yes, the skill provides a /cfe-validate command to perform local validation on the resulting extension. This verifies that the generated Adopted metadata XML and ChildObjects structure are correct.

What is the best way to intercept existing methods in a 1C configuration extension?

The best way to intercept existing methods is to borrow the base 1C metadata into your CFE extension. This generates ObjectBelonging=Adopted metadata, allowing you to safely extend and override existing object behaviors.

Why does my borrowed 1C form lose data bindings when adopted into an extension?

Borrowed 1C forms lose data bindings when adopted without specifying DataPath preservation. Using the -BorrowMainAttribute option ensures form data paths are bound correctly so subsequent edits maintain field connections.