tinyvue-develop-spec

Enforce standardized TinyVue component development practices across Vue 2/3 templates.

2.3k|352|Updated Nov 26, 2022
One-click install
npx skills add https://github.com/opentiny/tiny-vue --skill tinyvue-develop-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tinyvue-develop-spec
Source: https://github.com/opentiny/tiny-vue/tree/main/.agents/skills
Command: npx skills add https://github.com/opentiny/tiny-vue --skill tinyvue-develop-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

规范化 TinyVue 组件库的开发流程,确保跨版本、跨端的一致性与质量,降低重复工作与理解成本。

Core Features & Use Cases

该技能定义了组件库的结构与协作规范,包括模板分层、无渲染逻辑层的职责、设计规范注入、图标与主题协作、国际化与测试指南,以及文档开发的统一流程,适用于新增组件、重构与快速迭代的场景。

Quick Start

请阅读本 Skill 的 SKILL.md,并在新组件开发时严格按其中的前置条件、目录结构和设计规范执行。

Frequently Asked Questions about tinyvue-develop-spec

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

FAQPage Schema
How do I enforce consistent development practices across a Vue 2 and Vue 3 component library?

You can enforce consistent development practices by applying standardized component library rules that define cross-version templates, renderless architecture layers, design configurations, and documentation workflows.

What is renderless architecture in a cross-version Vue component library?

Renderless architecture separates component logic from presentation templates, ensuring consistent behavior across Vue 2 and Vue 3 while allowing flexible UI rendering and design configuration.

How to structure a new component for cross-version compatibility in a Vue component library?

Structure new components by following defined directory layouts, separating renderless logic layers, injecting design specifications, and configuring theming and internationalization according to the development standard.

Does this component library development specification support theming and internationalization workflows?

Yes, the specification defines explicit workflows and rules for theming, icon collaboration, and internationalization to ensure standardized component development and documentation across the repository.

Why do I need a SKILL.md front matter for component library validation and discovery?

A SKILL.md front matter with a name and description is required to provide explicit metadata like dependencies and components, which enables proper validation and discovery of the standardized component development rules.