docs-design

Generates versioned HTML design documents with embedded interactive prototypes in the docs directory.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/shengmingzhishu/LeeCommonVideoCut --skill docs-design-shengmingzhishu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-design
Source: https://github.com/shengmingzhishu/LeeCommonVideoCut/tree/main/.trae/skills/shared/docs-design
Command: npx skills add https://github.com/shengmingzhishu/LeeCommonVideoCut --skill docs-design-shengmingzhishu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping project design documentation consistent, versioned, and visually unified is hard when requirements iterate frequently. This Skill generates and maintains project-level design documents under /docs that combine project overview, feature descriptions, embedded interactive HTML prototypes, and interaction specs in a single file, with every iteration preserved as a new versioned file. ## Core Features & Use Cases - Versioned document generation: Creates files named {Chinese topic}-v{n}.html, scans /docs for the highest existing version, and never overwrites or deletes old versions. - Embedded interactive prototypes: Inlines HTML/CSS/JS prototypes with CSS scope isolation (.proto-{name}), IIFE-wrapped scripts, SVG icons, responsive breakpoints, and dark mode support. - Design system integration: Extracts colors, fonts, and style rules from the ui-ux-pro-max design system so all prototypes share a consistent visual language. - Use Case: When a product manager asks to add a new feature module to the reference image library design doc, the Skill scans /docs, finds 参考图库设计-v2.1.html as the latest, copies it to v2.2, inserts the new module section, and updates the changelog while leaving v2.1 untouched. ## Quick Start Ask the AI to write a project design document for your feature, for example: generate a design document with an interactive prototype for the reference image library feature.

Frequently Asked Questions about docs-design

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

FAQPage Schema
How do I create a project design document with an interactive prototype?▼

Describe the feature topic and requirements, and the Skill generates a single HTML file under /docs containing the project overview, feature descriptions, an embedded clickable prototype, and interaction tables. The prototype uses inline HTML, CSS, and JavaScript so it runs directly in a browser.

How are design document versions managed when requirements change?▼

Each iteration creates a new file named {topic}-v{n}.html with an incremented trailing version number, such as v2.1 to v2.2. The Skill scans /docs for the highest existing version of the same topic, copies it as a baseline, and never overwrites or deletes older files.

What naming rules apply to generated design document files?▼

File names must use a Chinese business topic extracted from the requirement plus a trailing version number, like 参考图库设计-v1.html. English words, pinyin, and generic names like design.html or project-design.html are prohibited.

What is the difference between docs-design and model-design?▼

docs-design produces project-level design documents stored in /docs with versioned history and embedded prototypes. model-design produces a single standalone HTML file for quick prototype validation that is not added to the documentation set. Both share the ui-ux-pro-max design system.

What design constraints must the embedded prototypes follow?▼

Prototypes must use inline SVG icons instead of emoji, keep transitions between 150-300ms, support 375/768/1024/1440px breakpoints, handle prefers-reduced-motion, maintain 4.5:1 contrast, and isolate styles with .proto-{name} prefixes to avoid cross-module pollution.