screen-spec-generator

Generate Flutter screen specifications from project structure analysis.

3|Updated Sep 29, 2025
One-click install
npx skills add https://github.com/xtone/ai_development_tools --skill screen-spec-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screen-spec-generator
Source: https://github.com/xtone/ai_development_tools/tree/main/flutter_development/skills/screen-spec-generator
Command: npx skills add https://github.com/xtone/ai_development_tools --skill screen-spec-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the manual creation and maintenance of Flutter screen specifications, reducing repetitive work and ensuring consistency across projects.

Core Features & Use Cases

  • Automatically analyze Flutter project structure and extract screen metadata (UI, state management, and routing information).
  • Generate per-screen definition documents and support updates via difference detection.
  • Use cases include creating new screen definitions, updating existing ones, and aligning definitions with project conventions.

Quick Start

Activate the skill by saying "画面定義書を作成したい" and provide the target screen file path to generate its definition.

Frequently Asked Questions about screen-spec-generator

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

FAQPage Schema
How do I automatically generate Flutter screen specifications from my existing code?

To automatically generate Flutter screen specifications, you provide a target screen file path and the tool analyzes the project structure including UI, state management, and routing to output Markdown definitions.

What is the best way to update existing Flutter screen definition documents?

The best way to update existing Flutter screen definition documents is through difference detection, which analyzes modified project structure and aligns per-screen definitions with current project conventions.

Can I analyze Flutter state management and routing when creating screen specs?

Yes, you can analyze Flutter state management and routing when creating screen specs. The process automatically extracts this metadata from the project structure to populate the final definition documents.

Does the generated Flutter screen specification support formats other than Markdown?

Yes, the generated Flutter screen specification supports formats other than Markdown. Alongside required Markdown templates and a command script, the process can output optional HTML artifacts.

How do I start creating a screen definition for a specific Flutter file?

To start creating a screen definition, activate the process by stating you want to create a definition and then provide the target screen file path to generate the required Markdown templates automatically.

Why should I use automated templates for Flutter documentation instead of writing manually?

You should use automated templates for Flutter documentation to reduce repetitive manual work and ensure consistency across projects by aligning generated definitions with established project conventions.