What problem does it solve? Designing managed forms in 1C:Enterprise without established patterns leads to inconsistent layouts, ad-hoc element naming, and rework during Configurator implementation or programmatic BSL form construction. ## Core Features & Use Cases - Form Archetypes: Ready-made structural templates for document forms, data processor forms, list forms, catalog item forms, and wizards, including events and properties. - Naming Conventions: Standardized names for groups, elements, and event handlers (e.g., HeaderGroup, Filter[Field]Use, ПриИзменении suffixes) to keep form code consistent. - Advanced Patterns: Collapsible groups, warning banners, popup menus in command bars, hyperlink labels, and forms without standard command bars, plus a full DSL example. - Use Case: When a change request requires a new data processor form, pick the Data Processor archetype, apply the naming conventions, and hand the layout to the Configurator or generate programmatic BSL elements. ## Quick Start Ask the assistant to design a managed form layout for a 1C document or data processor using the standard form archetypes and naming conventions.