role-compile

Compile 1C role metadata and rights from JSON DSL into XML files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the repetitive, error-prone work of hand-authoring 1C role metadata and rights by letting you define roles in a concise JSON DSL and compiling them into the required XML files.

Core Features & Use Cases

  • Compiles role metadata: Converts a JSON definition into Roles/Имя.xml with a generated UUID and Russian synonym/comment fields.
  • Generates rights XML: Produces Roles/Имя/Ext/Rights.xml with global flags, per-object rights, and optional RLS (restriction-by-condition) templates and conditions.
  • Supports shorthand + presets: Uses ObjectType.ObjectName: @view|@edit or explicit ObjectType.ObjectName: Right1, Right2, plus an object form for overriding rights and adding RLS rules.
  • Type and right aliasing: Accepts Russian type and right names (e.g., Справочник → Catalog, Просмотр → View) and normalizes them to canonical English names for XML generation.
  • Registers the role: Attempts to add the <Role> entry into Configuration.xml under <ChildObjects>.

Quick Start

Ask the AI to compile a new role from your role JSON DSL file into a specified 1C configuration export directory by running the role-compile command with JsonPath pointing to your JSON and OutputDir pointing to your target Configuration.xml root.

Frequently Asked Questions about role-compile

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

FAQPage Schema
How do I generate 1C role and rights XML from a JSON file?▼

Generating 1C role and rights XML from a JSON file requires compiling a JSON DSL into Roles/RoleName.xml and Rights.xml. You provide the JSON path and output directory, and the compiler translates shorthand presets into structured metadata with generated UUIDs.

Can I use Russian aliases for 1C access rights and metadata objects in my JSON DSL?▼

Yes, you can use Russian aliases for 1C access rights and metadata objects in your JSON DSL. The compiler translates Russian names like Справочник to Catalog and Просмотр to View, normalizing them into canonical English identifiers for XML generation.

How do I add RLS restriction templates when creating a new 1C role?▼

To add RLS restriction templates when creating a 1C role, include condition rules in your JSON DSL object definitions. The compiler processes these overrides and emits the RLS templates directly into the generated Rights.xml file.

What is the best way to automate 1C role creation for multiple metadata object types?▼

Automating 1C role creation for multiple metadata object types is best handled by defining shorthand presets like @view or @edit in a JSON DSL. This compiles per-object rights for Catalogs, Documents, and Registers into XML without manual authoring.

Does the generated 1C role automatically register in the Configuration.xml file?▼

Yes, the generated 1C role automatically registers in the Configuration.xml file. The compiler attempts to add the new Role entry under the ChildObjects node when the target Configuration.xml is available in the specified output directory.

What shorthand syntax can I use to define 1C document and catalog access rights?▼

You can define 1C document and catalog access rights using shorthand syntax like ObjectType.ObjectName: @view or @edit. The compiler expands these presets into explicit right lists within the generated XML metadata files.