myb-p-form-ruleslisted

Configure form rules (חוקי טופס) on MyBusiness CRM form/card pages — conditional hide/show, conditional required, readonly/lock, fixed/dynamic values, formulas, validation messages, URL-prefill. Form rules have NO admin UI — MCP is the only authoring path — so invoke this skill for ANY form-rule request and for WP7 (חוקי טופס) of the build work plan. Triggers: 'שדה חובה רק כשסטטוס = X', 'תסתיר את השדה עד שנבחר סוג', 'תנעל את הכרטיס אחרי סגירה', 'ערך ברירת מחדל בטופס', 'הצג הודעת אזהרה בטופס', 'חוקי טופס', 'שדה לקריאה בלבד', 'make this field required when', 'hide the field unless', 'lock fields after closing', 'readonly when status is', 'form rules', 'conditional mandatory field', 'auto-fill from another field'. NOT for server-side automations/emails on save — use myb-p-trigger-setup; NOT for page layout/sections — use myb-p-page-builder; NOT for access control/CLP — use myb-p-users-roles-permissions; NOT for table-view columns or row coloring — use myb-p-page-tables.
AviMYB/mybusiness-plugins · ★ 2 · API & Backend · score 63

Install: claude install-skill AviMYB/mybusiness-plugins

# Form Rules / חוקי טופס Author client-side field behavior on MyBusiness CRM form (card) pages: conditional hide, conditional required, readonly/lock, fixed values, live field mirroring, formulas, warning messages, and URL-prefilled fields. **Why this skill exists:** form rules are the only customization domain in the product with **no admin UI** — they are configured exclusively via MCP/API. The AI agent is the author of record; there is no "do it in the UI" fallback for the rules themselves. **Canonical mechanism doc (read before any non-trivial rule):** `../myb-p-kb/references/30-customization/07-form-rules.md` — rule object shape, condition grammar, the full action list, tool semantics, worked patterns, and limitations. This skill is the procedure; that file owns the facts. ## Boundaries — what this skill is NOT | The ask | Route to | |---|---| | Act on save / send email / create-update other records / server-side enforcement | `myb-p-trigger-setup` (form rules are client-side UX only — API writes bypass them; KB doc §1) | | Add/move fields, sections, tabs, widgets on the card | `myb-p-page-builder` | | Who may read/write a table or field (CLP, roles) | `myb-p-users-roles-permissions` | | Table-view columns, filters, conditional row coloring | `myb-p-page-tables` | | Filter a Pointer dropdown's options by another field | Not a rule action — native parent/child mechanism; `myb-p-parent-child-fields` (KB doc §6) | ## Pipeline placement — WP7 This skill executes **WP7