form-patterns

Provides design archetypes and naming conventions for composing managed 1C forms.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork in designing managed forms in 1C by providing proven layout archetypes and naming conventions, so your form UI stays consistent and easier to maintain.

Core Features & Use Cases

  • Form archetypes: Document forms, processing (DataProcessor) forms, list forms, catalog item forms, and wizards with recommended structure.
  • Event & property presets: Common event sets (e.g., OnCreateAtServer / OnOpen / NotificationProcessing) and typical properties like autoTitle and command-bar/window modes.
  • Naming conventions: Standard group/element names (e.g., ГруппаШапка*, Отбор[Поле], command button suffixes) to make generated and reviewed UI elements predictable.

Quick Start

Use the form-patterns skill to select the closest archetype (e.g., “document form”), apply its naming and layout order, and then design the form via /form-compile for the required layout.

Frequently Asked Questions about form-patterns

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

FAQPage Schema
How do I design consistent 1C managed forms without UI layout inconsistencies?

To design consistent 1C managed forms, apply proven layout archetypes and standard naming conventions for documents, lists, and catalogs, which reduces guesswork and makes your form UI easier to maintain.

What naming conventions should I use for 1C form groups and elements?

Standard 1C form naming conventions include prefixes like ГруппаШапка for header groups, Отбор[Поле] for filters, and specific command button suffixes to make generated and reviewed UI elements predictable.

What are the typical events and properties for 1C managed forms?

Typical 1C managed form events include OnCreateAtServer, OnOpen, and NotificationProcessing, while common properties involve autoTitle and specific command-bar or window modes to ensure proper structure.

Does this form design approach support both document forms and wizard forms in 1C?

Yes, this approach supports common 1C form types including document forms, data processor forms, list forms, catalog item forms, and wizards during the specification-to-implementation workflow.

What is the best way to structure a 1C catalog item form during specification-to-implementation?

The best way to structure a 1C catalog item form is to select the closest layout archetype, apply its recommended section order and naming patterns, and then compile the required layout.