admin-page-ui

Enforce consistent admin page UI patterns for lists, details, and containers.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/OZVE/cuarta-avenida --skill admin-page-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admin-page-ui
Source: https://github.com/OZVE/cuarta-avenida/tree/main/.claude/skills/admin-page-ui
Command: npx skills add https://github.com/OZVE/cuarta-avenida --skill admin-page-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce consistent admin page UI patterns across list pages, detail pages, containers, action menus, empty states, and delete flows, ensuring cohesive experiences in packages/admin.

Core Features & Use Cases

  • Enforces standard UI patterns for admin pages (list, detail, containers, and actions) to maintain consistency.
  • Guides implementation with hard rules, recommended patterns, and references for common admin UI tasks.
  • Provides ready-to-follow structures for container sections, action menus, delete confirmations, empty states, and typography.

Quick Start

Follow the guidance in this skill when scaffolding or modifying admin pages to ensure consistent lists, details, and actions.

Frequently Asked Questions about admin-page-ui

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

FAQPage Schema
How do I enforce consistent admin UI patterns across different React pages?

You can enforce consistent admin UI patterns by applying hard UI rules and design-pattern references that standardize how lists, detail pages, and containers render. This ensures uniform behavior and cohesive experiences across all admin pages.

What is the best way to standardize empty states and delete flows in a frontend design system?

The best way to standardize empty states and delete flows is by following ready-to-follow structural references and hard UI rules. This provides specific design-pattern guidance to ensure uniform behavior and cohesive experiences across admin pages.

Can I use this approach to scaffold action menus and container sections for Medusa-like UI standards?

Yes, this approach supports scaffolding action menus and container sections by guiding conformance to Medusa-like UI standards. It imposes hard UI rules and provides ready-to-follow structures to ensure uniform behavior across admin interfaces.

Do I need specific dependencies to maintain consistency in admin list and detail pages?

No specific dependencies are required to maintain consistency in admin list and detail pages. The framework operates independently by imposing hard UI rules and providing design-pattern references to standardize rendering and behavior.