What problem does it solve? Choosing the wrong metadata class in 1C:Enterprise — for example modeling an extensible set of kinds as an enumeration or typing a composite attribute with primitive types — leads to slow queries, forced restructuring, and painful migrations. This Skill guides the decision of which object class holds business data and how its attributes are typed, following platform standards and diagnostics. ## Core Features & Use Cases - Class selection: Maps business questions to the right metadata class — catalog, document, enumeration, chart of characteristic types, constant, or register — based on who is allowed to change the set of values. - Attribute typing: Enforces deliberate typing rules for string lengths, composite reference-only types, defined types, and common attributes, citing standards std432, std704, std728 and diagnostics АПК:1329, АПК:1330. - Predefined items and presentations: Covers predefined data update modes, interactive-deletion rights checks, and naming/presentation conventions (АПК:93, АПК:1207). - Use Case: When a requirement says "customers will add their own attribute kinds later", the Skill steers you to a chart of characteristic types instead of an enumeration, then creates and verifies the object via Unica MCP tools. ## Quick Start Ask the assistant to model a new business entity in the 1C configuration, for example: decide which metadata class should store product certifications and create it with properly typed attributes.
