myb-p-create-settings-pagelisted

Create a 'System-Tables'-style settings/admin page in MyBusiness CRM for managing the values of a lookup/status table (e.g. SupplierStatuses, ProjectStatuses, any custom <Entity>Statuses / <Entity>Types / <Entity>Priorities) with inline add / edit / delete, matching the built-in System-Tables-Task-Statuses / System-Tables-Sale-Statuses pages. Use this skill whenever the user wants an admin/settings screen where users (usually Admins) can add and edit the option values of a custom lookup table -- phrases like 'add a settings page for statuses', 'let users add/edit statuses in settings', 'create a System-Tables page', 'manage lookup values', 'a settings page like the other settings pages', 'עמוד הגדרות לסטטוסים', 'שיוכל להוסיף ולערוך סטטוסים במסך ההגדרות', 'עמוד ערכי מערכת', 'הגדרות לטבלת ערכים'. Use it AFTER the lookup table already exists (often right after myb-p-create-entity). It does NOT create the table itself.
AviMYB/mybusiness-plugins · ★ 2 · Web & Frontend · score 63

Install: claude install-skill AviMYB/mybusiness-plugins

# Create Settings Page (System-Tables style) / יצירת עמוד הגדרות לערכי מערכת Build a settings page that looks and behaves like MyBusiness's built-in **System-Tables-\*** pages (e.g. `System-Tables-Task-Statuses`, `System-Tables-Sale-Statuses`): a cog-headed page with the settings side-nav, a white card, an **inline-editable table** with an "הוסף ערך" (Add value) button, and a "< חזרה להגדרות" back link. The user manages the rows (add / edit / delete) of a small lookup table — statuses, types, priorities, categories — directly in the grid. > ## ⚠️ Read this first — the settings side-nav > > This skill reliably produces a working, role-gated settings page with inline > add/edit/delete, **and you CAN get the link into the settings side-nav** — as long as you edit the > *right* menu (Phase 6). The side-nav (`menuHolder2`) renders **live** from the menu its > `data-menu-id` points to, so adding your page to *that* menu makes the link appear and highlight as > "current". **The one narrow gap that remains:** MCP cannot change *which* menu the page binds to > (the `data-menu-id` lives in page HTML), so your link lands in whichever menu the template you > copied was bound to — which is usually **shared** with sibling settings pages, so it shows in their > side-navs too. A truly dedicated nav group requires the Simbla page-builder UI. The **direct URL > always works** regardless. See **Phase 6** and **Known limitations**. --- ## When to use / not use **Use** when a lookup/option t