cf-init

Generate an empty 1C:Enterprise configuration scaffold with Configuration.xml and a Russian language file.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill cf-init-arman-kudaibergenov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-init
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/cf-init
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill cf-init-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When you need to start a new 1C:Enterprise 8.3 project from a blank base, manually creating a correct initial configuration structure is slow and error-prone.

Core Features & Use Cases

  • Generates a valid empty configuration scaffold: creates Configuration.xml plus a default Russian language file.
  • Configurable essentials for a new base: sets configuration name, synonym, optional vendor and version, and compatibility mode for the new scaffold.
  • Use Case: Starting a brand-new empty managed-application configuration so you can immediately proceed with metadata compilation and further object creation.

Quick Start

Tell the AI to run /cf-init with your configuration name to generate the new scaffold in your chosen output folder.

Frequently Asked Questions about cf-init

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

FAQPage Schema
How do I create an empty 1C:Enterprise configuration scaffold?

To create an empty 1C:Enterprise configuration scaffold, you need to generate a valid Configuration.xml file along with a default Russian language file. This provides a clean configuration baseline required before initiating metadata compilation or creating new managed application objects.

What is a Configuration.xml file used for in 1C project initialization?

A Configuration.xml file is used during 1C project initialization to define the essential metadata structure of a new configuration. It stores the configuration name, synonym, vendor, version, and compatibility mode required to establish a valid project baseline.

How do I set the compatibility mode and vendor when initializing a new 1C configuration?

You can set the compatibility mode and vendor when initializing a new 1C configuration by providing these details as optional parameters alongside the mandatory configuration name. This generates a properly configured Configuration.xml scaffold tailored to your project requirements.

Can I overwrite an existing Configuration.xml file during 1C scaffold generation?

No, you cannot overwrite an existing Configuration.xml file during 1C scaffold generation. The tool explicitly refuses to overwrite an existing file to prevent accidental data loss, ensuring your current configuration metadata remains protected.

Do I need a specific output directory to generate 1C configuration metadata?

Yes, you need to specify an OutputDir to generate 1C configuration metadata. The scaffold generation process outputs the newly created Configuration.xml and default language file directly into the directory you define.