wot-ui-component-baseline

Enforce shared directory, naming, and validation rules for Wot UI components.

284|31|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/wot-ui/wot-ui --skill wot-ui-component-baseline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wot-ui-component-baseline
Source: https://github.com/wot-ui/wot-ui/tree/main/.agents/skills/wot-ui-component-baseline
Command: npx skills add https://github.com/wot-ui/wot-ui --skill wot-ui-component-baseline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized set of rules and conventions to ensure all Wot UI components adhere to a unified structure, naming, and documentation standard across creation, demos, and migration tasks.

Core Features & Use Cases

  • Directory and file conventions for component packages, including source, demo pages, docs, and typings.
  • Clear naming and organization rules to maintain consistency across the component ecosystem.
  • Verification and governance principles that guide when and how to apply the baseline, plus how to validate changes.
  • Apply to tasks such as creating new components, updating demos, or migrating documentation to the standardized layout.

Quick Start

Apply the wot-ui component baseline to new or migrating components to ensure consistent structure, naming, and documentation.

Frequently Asked Questions about wot-ui-component-baseline

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

FAQPage Schema
How do I standardize uni-app component directory structure and naming conventions?

To standardize uni-app component directory structure and naming conventions, apply a shared baseline that codifies source, demo, docs, and typings file organization to ensure ecosystem consistency.

What is a component baseline and why do I need it for Wot UI?

A component baseline is a centralized set of rules ensuring Wot UI components adhere to unified structure, naming, and documentation standards across creation, demos, and documentation migration tasks.

How do I migrate existing component documentation to a standardized layout?

To migrate existing component documentation to a standardized layout, apply the component baseline rules to reorganize directory structure, update naming conventions, and validate consistency across sources and docs.

Can I use this baseline for both creating new components and updating demos?

Yes, you can use this baseline for both creating new components and updating demos, as it applies governance principles and validation checkpoints to ensure consistent structure across all component-related tasks.

What's the best way to enforce consistency across a uni-app component ecosystem?

The best way to enforce consistency across a uni-app component ecosystem is to apply a centralized baseline that codifies directory structure, naming rules, and documentation standards with validation checkpoints.