cfe-init

Generate scaffold files for new 1C configuration extensions.

140|16|Updated May 2, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica --skill cfe-init-ingvarconsulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfe-init
Source: https://github.com/IngvarConsulting/unica/tree/main/plugins/unica/skills/cfe-init
Command: npx skills add https://github.com/IngvarConsulting/unica --skill cfe-init-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of scaffold files for 1C configuration extensions, streamlining the setup process for developers.

Core Features & Use Cases

  • Extension Scaffolding: Generates initial XML, language, and role files for new 1C extensions.
  • Config Enhancement: Facilitates auto-detection of configuration paths and compatibility modes based on existing project files.
  • Use Case: A developer needs to start a new extension project; simply running this Skill sets up all necessary files with correct parameters ready for further customization.

Quick Start

Use the cfe-init skill to generate a new 1C extension named "MyExtension" with default settings.

Frequently Asked Questions about cfe-init

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

FAQPage Schema
How do I create scaffold files for a 1C configuration extension?

To create scaffold files for a 1C configuration extension, you can use automation to generate initial XML, language, and role files based on parameters like name, purpose, version, and vendor. This ensures a consistent project structure ready for further customization.

What is the best way to automate 1C extension project setup?

Automating 1C extension project setup is best achieved by generating parameterized scaffold files. This method auto-detects configuration paths and compatibility modes from existing project files, streamlining the creation of necessary XML and role structures.

Do I need existing project files to generate a 1C configuration extension?

You need access to existing project files or user input to generate a 1C configuration extension. These files are required for auto-detecting configuration paths and determining compatibility modes during the scaffolding process.

Can I specify a custom vendor and version when scaffolding a 1C extension?

You can specify a custom vendor and version when scaffolding a 1C extension. The generation process supports parameterized inputs by name, purpose, version, vendor, and path detection to tailor the output files.

How does auto-detection of configuration paths work for 1C extensions?

Auto-detection of configuration paths works by scanning existing project files to determine the correct locations and compatibility modes. This ensures the newly generated 1C extension scaffold aligns seamlessly with the current project structure.