Instruction file imported from ViktorErmakov/OneSniffer (
.cursor/rules/forms.mdc). Copyright stays with the author.
Managed Forms — Entry Point
This file is the router for managed-form work. Load it first, then load only the companion rules selected by the table below — companion files are not auto-attached by file pattern.
Routing
| Task | Load |
|---|---|
Create or structurally modify Form.xml |
forms-add.md, metadata-xml-workarounds.md |
| Add or rename form event handlers | forms-events-add.md, form-module.md |
Edit Form.Module.bsl logic |
form-module.md |
| Set up module regions in a new form module | module-structure.md → Form Module (5 mandatory regions) |
| Server-side form-module code (reserved names) | form-reserved-names.md |
| Client-server architecture (directives, round trips) | dev-standards-architecture.md §3 → "Client-Server Interaction", anti-patterns.md → "Excessive Client-Server Calls", anti-patterns.md → "Using &НаСервере Instead of &НаСервереБезКонтекста" |
Client-side async code (Асинх / Ждать) |
async-methods.md |
| Programmatic modification of typical forms (element placement, fill checking, form commands) | dev-standards-forms.md |
| Working on an adopted form of an extension | extension-patterns.md, dev-standards-architecture.md §2 |
Each companion file is self-contained — load only the ones that match the task. Do not preload the whole set "to be safe".