form-patterns

Structure 1C managed forms using archetypes and naming conventions.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill form-patterns-comol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-patterns
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/source/form-patterns
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill form-patterns-comol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Справочник паттернов компоновки управляемых форм 1С — архетипы, конвенции именования и продвинутые приёмы, помогающие стандартизировать и ускорить проектирование форм.

Core Features & Use Cases

  • Архетипы форм: Форма документа, Форма обработки (DataProcessor), Форма списка, Форма элемента справочника, Мастер (Wizard)
  • Конвенции именования и структурирование групп, страниц и реквизитов
  • Продвинутые паттерны компоновки и поведенческие соглашения для ERP-форм

Quick Start

Выбери подходящий архетип и применяй конвенции именования перед проектированием управляемой формы.

Frequently Asked Questions about form-patterns

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

FAQPage Schema
What are the standard archetypes for 1C managed forms?

1C managed forms archetypes cover document forms, data processor forms, list forms, catalog item forms, and wizards. They help developers structure and standardize UI layout patterns from initial sketch to final implementation.

How do I structure groups and attributes in 1C managed forms?

You structure 1C managed forms by applying naming conventions and predefined layout patterns for groups, pages, and attributes. This standardizes the form design and accelerates the implementation process across different ERP forms.

What is the best way to standardize 1C form design across an ERP project?

The best way to standardize 1C form design is by selecting an appropriate form archetype and enforcing naming conventions alongside advanced layout patterns. This ensures consistency across document forms, data processors, and lists.

Does this approach work for both 1C document forms and list forms?

Yes, this approach works for 1C document forms, list forms, data processor forms, and catalog item forms. The established archetypes and naming conventions are applicable across all these managed form types.

When do I need to use advanced layout patterns for 1C managed forms?

You need advanced layout patterns for 1C managed forms when designing complex ERP interfaces that require specific behavioral agreements and structured grouping beyond the basic archetype templates.