design

Generate consolidated screen design documentation for legacy projects.

Updated Feb 6, 2026

Search Tags:#design #documentation #wireframes #screen-design #legacy-support #UI-specs

Ready to run

npx skills add https://github.com/sizukutamago/blueprint-plugin --skill design-sizukutamago

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design
Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/design
Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill design-sizukutamago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This unified screen design skill consolidates UI layout, wireframes, screen flows, and UI specifications into a single reference, preserving legacy workflows for teams that relied on a single, all-in-one skill.

Core Features & Use Cases

Centralized guidance for screen design artifacts (layout, wireframes, transitions, component catalogs).
Backward-compatible documentation generation to support ongoing projects while migration occurs.
Use Case: When maintaining an older project, teams can still generate consistent design docs and references before migrating to split skills like design-inventory (Wave A) and design-detail (post-B).

Quick Start

Use the design skill to generate the core screen design documents for an existing project and begin planning the migration to the split skills.

Frequently Asked Questions about design

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

FAQPage Schema

How do I generate UI specifications and wireframes for a legacy screen design project?▼

To generate UI specifications and wireframes for a legacy screen design project, use this skill to consolidate UI layout, screen flows, and component catalogs into a single backward-compatible reference document. It preserves older workflows while planning migration to split skills.

What is the best way to maintain screen design documentation before migrating to split skills?▼

The best way to maintain screen design documentation before migrating is using this unified skill to produce centralized references. It ensures consistent generation of legacy UI specs and wireframes until your team transitions to the dedicated design-inventory and design-detail skills.

Can I use this skill for new screen flows and component catalogs, or is it only for legacy support?▼

You can use this skill for new screen flows and component catalogs, but it is specifically designed for legacy support. It provides backward-compatible documentation generation to maintain ongoing projects while migrating toward the split design-inventory and design-detail skills.

How do I transition from a unified screen design artifact to split skills like design-inventory and design-detail?▼

To transition from a unified screen design artifact to split skills, first use this skill to generate your core screen design documents for the existing project. Then, begin planning your migration to design-inventory for Wave A and design-detail for post-B phases.

When should I not use this unified UI layout and wireframes skill?▼

You should not use this unified UI layout and wireframes skill if your project is new and not tied to legacy workflows. Because it is deprecated, new projects should directly adopt the split skills, design-inventory and design-detail, for generating component catalogs and UI specifications.