backend-ui-design

Design backend admin pages with @open-mercato/ui components and layouts.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/comerito/om-hackathon-starter --skill backend-ui-design-comerito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-ui-design
Source: https://github.com/comerito/om-hackathon-starter/tree/main/.ai/skills/backend-ui-design
Command: npx skills add https://github.com/comerito/om-hackathon-starter --skill backend-ui-design-comerito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design and implement consistent backend/backoffice interfaces using the @open-mercato/ui library. Use when building admin pages, CRUD interfaces, data tables, forms, detail pages, or any backoffice UI.

Core Features & Use Cases

  • Reuse the library's components to ensure visual and interaction consistency across all admin screens.
  • Standardize layouts, data presentation, and form patterns to reduce custom implementations.
  • Improve accessibility and keyboard navigation across backend pages.

Quick Start

Start by designing a backend admin page using the standard components from the library to ensure a consistent UI.

Frequently Asked Questions about backend-ui-design

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

FAQPage Schema
How do I build consistent admin panels using a UI library?

Build consistent admin panels by reusing the @open-mercato/ui library's core components, which standardize layouts and data presentation across all backend backoffice screens to ensure visual and interaction consistency.

What is the best way to standardize data tables and forms in a backend interface?

The best way to standardize data tables and forms in a backend interface is to use the @open-mercato/ui library, which enforces standardized data presentation and form patterns to reduce custom implementations.

Can I use @open-mercato/ui for CRUD interfaces and detail pages?

Yes, you can use @open-mercato/ui for CRUD interfaces and detail pages. The library provides guided component usage and layout patterns specifically scoped for building these backend backoffice interfaces.

Does @open-mercato/ui enforce keyboard navigation and accessibility for backend UI?

Yes, @open-mercato/ui enforces explicit keyboard navigation and accessibility requirements across backend pages, ensuring that admin panels and data tables are accessible to all users.

Why does my backend UI design lack consistency across different admin screens?

Your backend UI design lacks consistency due to custom implementations. Using the @open-mercato/ui library standardizes layouts, data presentation, and form patterns to eliminate visual and interaction discrepancies.