myb-p-create-entitylisted

Create a complete new custom entity (module) in MyBusiness CRM -- tables, fields, sample data, list page with inline edit, custom JS, and menu integration. Use this skill whenever the user wants to create a new entity, new module, new object type, add a new business concept to the CRM, or build a full CRUD workflow for a custom table. Examples: creating an Affiliates module, a Suppliers entity, a Projects entity, a Vehicles table, an Inventory system, a Courses module, or any custom entity with its own list page. Also use when the user mentions: ישות חדשה, מודול חדש, טבלה חדשה עם דפים, יצירת ישות, בניית מודול, create entity, create module, new entity, new table with pages, custom object, new CRUD module. This skill orchestrates multiple tools together -- it is the right choice when the user needs the full package (tables + list page + data + menu).
AviMYB/mybusiness-plugins · ★ 2 · Data & Documents · score 63

Install: claude install-skill AviMYB/mybusiness-plugins

# Create Entity / יצירת ישות חדשה Build a complete custom entity in MyBusiness CRM -- from database tables through a fully functional list page with inline editing. ## CRITICAL READ FIRST — Known Platform Bugs These bugs affect EVERY run of this skill. Design around them from the start: ### Constraint 1: `Create-Form-Page` produces NewMaster-based pages — works in iframe, NOT via direct URL `Create-Form-Page` MCP always assigns `NewMaster` as the masterPage. The actual `NewMaster.js` source has the relevant logic gated on `if (!Simbla.User.current()) {...}` — i.e., it only matters for **anonymous** users (public landing forms). For authenticated CRM users: - The `console.error("missing uuidVal")` line is just a log, not a fatal error. - Standard form load via iframe + `data-edit-view="modal-left"` / `"modal-right"` works. - Opening a NewMaster-based page via direct URL (`apps/mybusiness/Entity?oid=X`) shows empty fields — NewMaster doesn't fall back to URL params. There is **NO MCP tool or Parse API** to change `masterPageId` of an existing page. Pages are in a Simbla-private collection, not in Parse classes. **→ Decision tree:** - User wants click-to-edit on a list row, opening a full card view? → **Build the form page (Phase 4) and link via `modal-left` + `useIframe: true`** (this is the default workflow now). - User wants the **Name cell itself** (not just the pencil) to open the card? → Same mechanism, wired by the template: the Name is wrapped in `a.entity-link`