admin-design-system

Enforce design schema adherence and isolation for Goliath admin pages.

Updated May 13, 2026

Search Tags:#consistency #isolation #design rules #design-system #admin pages #Goliath app

Ready to run

npx skills add https://github.com/dloschiavo/orca --skill admin-design-system

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: admin-design-system
Source: https://github.com/dloschiavo/orca/tree/main/recipes/admin-design-system
Command: npx skills add https://github.com/dloschiavo/orca --skill admin-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the need for consistent design and isolation between admin and public pages in a Goliath app, reducing visual inconsistencies and simplifying maintenance.

Core Features & Use Cases

Design Reusability: Leverages existing design tokens/components where available for admin pages.
Typical Admin Backend: Defines standard conventions for page shells, cards, tables, forms, buttons, badges, and icons when no existing designs are available.
Isolation Rule Adherence: Ensures admin pages do not share layout, design, or asset files with public-facing pages.
Pre-Flight Checklist: Provides a list of checks to ensure adherence to design rules before deployment.

Quick Start

Run the skill on admin pages to ensure adherence to design guidelines.

Frequently Asked Questions about admin-design-system

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

FAQPage Schema

How do I ensure consistent design between admin and public pages in a Goliath app?▼

To ensure consistent admin design in a Goliath app, you enforce adherence to established design schemas and leverage existing design tokens. This approach maintains visual coherence while simplifying the maintenance of internal and external UIs.

Why should admin pages be isolated from public-facing layouts?▼

Admin pages require isolation to prevent shared layout, design, or asset files with public pages. This separation enforces strict visual coherence, reduces cross-contamination of styles, and simplifies the maintenance of internal backend interfaces.

What design conventions should I use for an admin backend when no existing designs are available?▼

For admin backends without existing designs, apply standard conventions for page shells, cards, tables, forms, buttons, badges, and icons. This establishes a predictable visual structure for internal tools without requiring UI design from scratch.

How do I validate that my admin pages meet design rules before deployment?▼

You validate admin pages before deployment by running a pre-flight checklist. This checklist ensures adherence to isolation rules and design schemas, confirming that internal UIs meet strict visual coherence standards prior to release.

Can I reuse existing design tokens and components for internal admin pages?▼

Yes, you can leverage existing design tokens and components for admin pages. Reusing available design elements ensures strict visual coherence between internal and public UIs while reducing development effort.