What problem does it solve?
Building backend and backoffice pages often leads to inconsistent custom tables, forms, and notifications across modules. This Skill enforces a single design system so every admin page in an Open Mercato project uses the same shared components, patterns, and interaction conventions.
Core Features & Use Cases
- Component-driven page construction: Mandates CrudForm for forms, DataTable for lists, flash() for notifications, and Page/PageHeader/PageBody layout primitives from @open-mercato/ui.
- Implementation checklist and anti-patterns: Provides a pre-flight checklist (keyboard shortcuts, loading/error/empty states, truncation, severity badges) and a list of anti-patterns such as custom tables, alert() calls, and hardcoded colors.
- API and custom-field integration patterns: Shows how to wire pages to backends via apiCall/createCrud/updateCrud helpers and how to render dynamic custom fields in forms, columns, and filters.
- Use Case: When adding a new CRUD module (e.g., an inventory items admin page), follow this Skill to assemble a FilterBar + DataTable list view, a dialog with an embedded CrudForm, and flash-based feedback without writing any bespoke UI.
Quick Start
Ask the agent to create a backend CRUD page for a new module following the backend UI design guidelines, using DataTable for the list and CrudForm for the create/edit dialog.