Generate a 1C:Enterprise configuration scaffold with XML metadata files.
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill cf-init-dach-coin
Please help me install this Agent Skill. Skill: cf-init Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/cf-init Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill cf-init-dach-coin
This Skill helps you quickly start a brand-new 1C:Enterprise 8.3 configuration without manually creating the required XML skeleton and localization files.
Configuration.xml with a new UUID set and a Russian script variant.Languages/Русский.xml so the configuration has a usable language entry.Synonym, Version, Vendor, and CompatibilityMode to match your target platform expectations.Use case: when beginning development for a new client configuration or a clean refactor branch, you can generate the baseline XML structure and then proceed to add objects (metadata) safely.
Ask the AI to run the cf-init skill to create a new blank 1C configuration named "МояКонфигурация" in the default src folder.
High-intent search queries and answers about installing and using this skill.
You create a blank 1C:Enterprise configuration by generating the required metadata XML files, specifically Configuration.xml and a Russian language file, for your new project name. This provides a baseline structure before adding metadata objects.
Bootstrapping a new 1C configuration requires writing a Configuration.xml file and a Languages/Русский.xml file to the target directory with UTF-8 BOM encoding to ensure proper structure and localization.
Yes, you can configure the compatibility mode and vendor when generating a 1C configuration scaffold. The process accepts optional parameters including Synonym, Version, Vendor, and CompatibilityMode to match target platform expectations.
Generating a 1C configuration scaffold supports adding custom synonyms and versions through optional parameters. You can pass a Name with optional Synonym, OutputDir, Version, Vendor, and CompatibilityMode to customize the baseline metadata.
The best way to set up a clean-start branch for 1C development is to generate an empty configuration scaffold with a new UUID set and baseline XML structure, then proceed to safely add metadata objects to the directory.
mmmmmm786mngb-jpgGenerate a minimal 1C configuration scaffold with Configuration.xml and Languages/Русский.xml.
Desko77Create 1C metadata objects with forms, subsystems, and validation.
Mineru98Add UTF-8 BOM to PowerShell .ps1 files recursively.
Arman-KudaibergenovGenerate an empty 1C:Enterprise configuration scaffold with Configuration.xml and a Russian language file.