module-placement

Assigns 1C:Enterprise code to object, manager, or common modules with correct context flags.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill module-placement-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-placement
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/module-placement
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill module-placement-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the wrong host module in a 1C:Enterprise configuration leads to broken client-server boundaries, unsafe server calls, and violations of development standards. This Skill decides where each piece of code belongs and configures the module correctly. ## Core Features & Use Cases - Module kind selection: Applies the std486 decision model to choose between object module, manager module, and common module based on instance state and metadata ownership. - Context and flag configuration: Picks exactly one of the four valid common module contexts (Server, ВызовСервера, Клиент, КлиентСервер) with matching postfix naming and Вызов сервера exposure rules. - Standards-backed review: Checks cached modules, presentation handlers, and first-launch/update handlers against standards 455-746 and АПК diagnostics using Unica MCP tools. - Use Case: When adding a pricing calculation to a catalog, the Skill maps the subsystem with unica.project.map, checks callers with unica.code.graph, creates a server common module with the correct postfix via unica.meta.add, and verifies the result with unica.code.diagnostics. ## Quick Start Ask the assistant to decide where a new 1C procedure should live and to create the module with the correct context flags and postfix.

Frequently Asked Questions about module-placement

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

FAQPage Schema
How do I choose between object module and manager module in 1C?▼

Use the object module when the code works with ЭтотОбъект instance state, and the manager module when the logic is static for the metadata object or operates on an already-written reference. Calling exported object module code from elsewhere forces a ПолучитьОбъект() read of the whole object.

What are the four valid common module contexts in 1C?▼

The four valid contexts are Server (postfix none or Сервер), Server for client calls (ВызовСервера), Client (Клиент or Глобальный), and Client-server (КлиентСервер). Any other flag combination violates АПК:125, and each context has a fixed set of client, server, and external connection flags.

When should I set the Вызов сервера flag on a common module?▼

Set Вызов сервера only for API genuinely called from the client, and state what it exposes. It is an exposure decision, not a convenience: the exposed API must not reveal data the user cannot see, and exported procedures must not take mutable types.

What restrictions apply to presentation handlers in a manager module?▼

Presentation handlers run on every presentation request, so they must contain no queries, no object fetching, no dotted access to reference attributes, and no reliance on predefined items that exchange may not have loaded yet, per std746 and std697.

Why must first-launch and update handlers be idempotent in 1C?▼

First-launch and release update handlers may run multiple times, so they must check for existence before creating data. In a distributed infobase they must not recreate or unconditionally rewrite data in a subordinate node, per std556.