1c-vendor-standards

What problem does it solve? AI agents working on 1C:Enterprise configurations often lack consistent knowledge of official vendor standards (v8std), leading to non-compliant metadata design, queries, transactions, and module code that fails review. ## Core Features & Use Cases - Domain Checklists: Condensed checklists across 11 domains including metadata naming, data storage, event handlers, queries, transactions, code modules, client-server, security, forms/UI, BSP libraries, and localization. - Role-Based Loading: Architect agents load it during design; reviewer agents load it when checking code against vendor standards; writer agents skip it. - Deep References: Each domain points to a detailed standard file (std-NN-<domain>.md) for in-depth reading when the checklist is insufficient. - Use Case: When designing a new document with register movements, the architect agent applies the data storage and transaction checklists, then reads std-05-transactions.md for locking details. ## Quick Start Ask the agent to review this 1C module against the vendor standards checklists and report any violations by domain.