form-patterns

Catalogues archetypes, event hooks, naming conventions and layout patterns for designing 1C managed forms.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill form-patterns-mmmmmm786mngb-jpg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-patterns
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/form-patterns
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill form-patterns-mmmmmm786mngb-jpg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a catalog of patterns and conventions to guide the design of managed 1C forms.

Core Features & Use Cases

  • Archetypes for common form types: document forms, data processors, and lists.
  • Naming conventions and layout patterns that promote consistency across forms.
  • Use Case: Before designing a form, refer to these archetypes to apply standard structures and terminology.

Quick Start

Consult this reference before designing a new 1C form to select an archetype and apply the conventions.

Frequently Asked Questions about form-patterns

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

FAQPage Schema
What are 1C managed form design patterns and when should I use them?

1C managed form design patterns are standardized archetypes, event hooks, naming conventions, and layout templates for documents, data processors, and lists. Use them before designing a new 1C form to enforce architecture consistency across your application.

How do I apply naming conventions to 1C managed forms?

Apply naming conventions to 1C managed forms by referencing the codified standard terminology within the form-patterns catalog. This reference provides consistent naming structures for form elements across document forms, data processors, and list archetypes to maintain architectural alignment.

Does this form-patterns reference cover archetypes for 1C data processors and lists?

Yes, this reference covers archetypes for 1C data processors and lists. It specifically codifies standard structures, event hooks, and layout patterns for these common managed form types alongside document forms to guide consistent architecture.

What's the best way to standardize layout patterns across multiple 1C documents?

The best way to standardize 1C document layouts is to select a matching document archetype from the form-patterns reference before development. Applying the provided layout patterns and conventions ensures structural consistency across all newly designed 1C managed forms.

Can I use these form archetypes when architecting event hooks for 1C managed forms?

Yes, you can use these form archetypes when architecting event hooks for 1C managed forms. The reference codifies standard event hooks alongside naming conventions and layout patterns specifically to guide and enforce consistent form architecture.