ui-architect

Enforce O2 component library and design token standards for Vue interfaces.

20.6k|992|Updated Feb 2, 2023
One-click install
npx skills add https://github.com/openobserve/openobserve --skill ui-architect-openobserve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-architect
Source: https://github.com/openobserve/openobserve/tree/main/.claude/skills/ui-architect
Command: npx skills add https://github.com/openobserve/openobserve --skill ui-architect-openobserve

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates UI inconsistency and technical debt in the OpenObserve web frontend by enforcing a strict, CI-validated design contract for all new and modified components.

Core Features & Use Cases

  • Design System Enforcement: Ensures all UI elements use the O2 component library, semantic design tokens, and a standardized spacing/radius scale.
  • Structural Guardrails: Standardizes page layouts, form containers, and data fetching patterns to ensure a uniform user experience across the entire application.
  • Use Case: When building a new settings page, this Skill guides you to use OPageLayout for the structure, OForm with Zod for validation, and semantic tokens for colors, ensuring the page integrates perfectly with the existing app shell.

Quick Start

Use the ui-architect skill to scaffold a new settings page that follows the O2 component library and design token standards.

Frequently Asked Questions about ui-architect

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

FAQPage Schema
How do I enforce UI consistency across Vue components in a web application?

To enforce UI consistency, apply architectural guardrails that govern Vue component implementation, design token usage, and layout structures. This ensures visual and functional uniformity by adhering to strict linting rules for CSS and spacing.

What is the best way to scaffold a settings page using a design system?

The best way to scaffold a settings page is using a standardized page layout component for structure, a form component with Zod for validation, and semantic design tokens for colors. This ensures the page integrates perfectly with the existing app shell.

Does this UI architecture approach work with Tailwind and Vue?

Yes, this UI architecture approach works with Vue and Tailwind by standardizing component composition and enforcing a strict design contract. It requires adherence to defined linting rules for CSS, spacing, and radius scales.

How do design tokens prevent frontend technical debt?

Design tokens prevent frontend technical debt by enforcing a standardized spacing, radius, and semantic color scale across all user-facing interfaces. This eliminates visual inconsistency by requiring all new components to use the defined component library.

Why does my frontend UI break when adding new components?

Frontend UI breaks when adding new components if they bypass the established design contract, causing visual inconsistency. Enforcing strict architectural guardrails for component composition and CSS linting standardizes the user experience.

Can I use Zod for form validation within a standardized UI layout?

Yes, you can use Zod for form validation within a standardized UI layout. The architecture guides you to use form containers with Zod validation alongside standardized page layouts to ensure a uniform user experience.