A routing guide for selecting product-design agent skills for tasks such as requirements, prototypes, databases, APIs, terminology, reviews, and change analysis. It chooses released skills based on the requested action and design area.
Instructions for routing product-design work to the right specialized skill. They cover activities such as requirements diagrams, prototypes, data models, API designs, reviews, and change-impact analysis.
A guide for designing and checking system interfaces, including REST APIs, integration messages, and optionally machine-readable OpenAPI 3.1 specifications.
Design or validate implementation-ready module boundaries, frontend/backend layering, dependency direction, contracts, quality gates, and traceability without generating business code. Use for code structure, module decomposition, layered architecture, bounded contexts, package layout, or development-ready…
A read-only analysis process for determining how a proposed change affects product designs and their supporting documents. It checks requirements, terminology, database design, APIs, prototypes, and existing reviews.
A read-only review process for checking whether product requirements, database designs, APIs, terminology lists, and prototypes fit together. It produces a score, tracked issues, evidence, and a recommended repair order.
A shared register for business terms, data fields, fixed value lists, and codes. It gives requirements, databases, interfaces, and screen designs one agreed name for each concept.
A database design tool for creating or checking entity-relationship diagrams, table structures, data dictionaries, indexes, and DDL. DDL is the SQL used to define database objects such as tables and indexes.
A document intake and completion tool for existing or unfinished design documents. It sorts requirements, database, interface, flowchart, and glossary files into a common structure and records what is missing.
A tool for creating and checking draw.io business swimlane flowcharts. Swimlanes separate the people or teams involved, while the chart shows activities, decisions, and how work moves between them.
A page-prototype annotation tool for turning a system feature into a detailed screen description. It documents page structure, fields, buttons, states, interactions, permissions, and links to related requirements and interfaces.
A requirements and design document skill for describing how a system works. It covers overall design, business processes, feature inputs and outputs, internal interfaces, permissions, data needs, and reports.
Use when: designing API contracts between frontend and backend based on prototype page inventory, defining request/response field structures, establishing naming conventions, and generating an api.md file per page for team alignment before coding. Triggers on: api contract, interface design, 接口约定, 前后端对齐, 字段定义, 接口设计…
A tool for turning business materials—such as prototypes, requirements documents, field lists, and data dictionaries—into a shared description of how a product works.
Use when: generating complete Vue 3 page code (index.vue + data.ts + modal components + api.md + pages.ts registration) from a prototype page inventory and API contract, strictly following the cx-ui-produce project conventions. Read SKILL.md first (rules+constraints), then read the matching TPL-.md for the template…
Use when: analyzing Axure exported HTML prototype files to extract page inventory, classify interaction patterns, identify reusable components, and produce a structured page checklist for Vue development. Also supports NON-standard detailed design documents (free-form MD/Word) or natural language descriptions as…
Use when: parsing STANDARD requirement-design specification documents produced by wl-skills-design (path contains .wl-skills/docs/spec/, files like ch1-3.md / 4.x-{module}.md / 4.N-data-report.md, with function codes like PMMB001, IPO tables containing 处理逻辑, and flow descriptions with five-elements) into the SAME…
Use when: auditing list pages for dict-rendered columns still shown as plain text and upgrading them to semantic auto-color tags (renderAutoTag/dictAutoTag). Triggers on: 状态列审计, 字典列Tag, 状态tag补齐, 列表彩色化, dict column audit, status tag scan, 存量改造.
Use when standardizing or migrating frontend Vite subapp environments. Triggers on: 标准环境配置, 前端环境标准化, 五套环境, 本地联调, public 联调, 172/9000 迁移, sit-api, uat-api, pre-api, prod-api, environment profile.