ui-spec

Generate UI screen specifications in Markdown from design goals and component requirements.

1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/infinith4/dev-ai-driven-development --skill ui-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-spec
Source: https://github.com/infinith4/dev-ai-driven-development/tree/main/.claude/skills/ui-spec
Command: npx skills add https://github.com/infinith4/dev-ai-driven-development --skill ui-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

このスキルは、UI/UX設計の画面仕様書作成を自動化し、手作業の抜け漏れを減らして設計と実装の間のギャップを埋めます。

Core Features & Use Cases

  • 自動画面仕様の生成: レイアウト、コンポーネント仕様、画面遷移を統一フォーマットで提供します。
  • 再利用可能なテンプレート: 画面タイプ別の標準テンプレートと共通コンポーネント定義を提供します。
  • 適用範囲: Web/モバイルアプリの設計プロセス全体で活用可能で、ワイヤーフレームから仕様書へ橋渡しを行います。

Quick Start

設計目標と仕様を入力すると、画面仕様書を自動生成します。

Frequently Asked Questions about ui-spec

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

FAQPage Schema
How do I automate UI screen specification creation from wireframes?

Yes, this UI screen specification generator applies to both web and mobile apps, providing standardized templates for component definitions and screen-flow documentation across the entire product design workflow.

What is the best way to document screen-flow and accessibility for UI design?

To generate a complete screen spec, provide your design goals and component requirements as input, and the system automates the creation of layout specifications, interaction definitions, and screen-flow documentation.

Can I use this for both web and mobile app screen specifications?

Yes, this UI screen specification generator applies to both web and mobile apps, providing standardized templates for component definitions and screen-flow documentation across the entire product design workflow.

What format are the generated UI screen specifications exported in?

The generated UI screen specifications are exported in Markdown with a defined output structure, including overview, screens, and references sections for easy integration into documentation workflows.

Do I need predefined component definitions to generate screen specs?

No, you do not need predefined components, but supplying component requirements alongside design goals allows the system to accurately automate layout specifications and interaction definitions within the output.