cfe-init

Generate a 1C configuration extension scaffold with Configuration.xml and language files.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill cfe-init-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfe-init
Source: https://github.com/msrv-tech/skills/tree/main/cfe-init
Command: npx skills add https://github.com/msrv-tech/skills --skill cfe-init-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This tool generates a ready-to-use scaffold for a 1C configuration extension (CFE), saving time when starting a new extension, patch, or customization.

Core Features & Use Cases

  • Create a scaffold including Configuration.xml, Languages/Русский.xml, and optional Roles directory.
  • Derive UUIDs and compatibility settings from an optional base configuration, enabling seamless integration with existing bases.
  • Quick-start-friendly: supply a Name and optional parameters to generate a working project skeleton.

Quick Start

Run the cfe-init script with -Name <YourExtension> to generate a new scaffold in the chosen OutputDir.

Frequently Asked Questions about cfe-init

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

FAQPage Schema
How do I create a new 1C configuration extension project scaffold?

To create a 1C configuration extension scaffold, run the cfe-init script with the -Name parameter. It generates a ready-to-use project structure including Configuration.xml and Languages/Русский.xml in your specified OutputDir.

What is a Configuration.xml file used for in 1C CFE development?

A Configuration.xml file defines the structure and metadata of a 1C configuration extension. This tool generates it automatically, handling UUID generation and resolving compatibility settings from a base configuration if provided.

Can I derive compatibility settings from an existing 1C base configuration?

Yes, you can derive CompatibilityMode and InterfaceCompatibilityMode from an existing base. Supply the -ConfigPath parameter pointing to your base configuration to resolve these settings automatically during scaffold generation.

Do I need to manually generate a UUID for a 1C configuration extension?

No, you do not need to manually generate a UUID. The scaffold generator handles UUID creation automatically, ensuring your new 1C configuration extension has a unique identifier without manual intervention.

What's the best way to start a 1C patch or customization project?

The best way to start a 1C patch or customization project is using a scaffold generator. It quickly creates the necessary Configuration.xml, language files, and an optional Roles directory, saving initial setup time.

Does the 1C extension scaffold include a Roles directory by default?

The 1C extension scaffold supports an optional Roles directory. It generates the core Configuration.xml and Languages/Русский.xml files, while including the Roles directory when your extension requires role definitions.