ui-discovery-formats

Generate standardized markdown UI discovery artifacts from raw screen lists.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill ui-discovery-formats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-discovery-formats
Source: https://github.com/FoxSilou/ConfigurationClaude/tree/main/.claude/skills/ui-discovery-formats
Command: npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill ui-discovery-formats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The UI discovery process often lacks consistent, reusable templates for screen inventories, user‑flow diagrams, and presenter specifications, leading to fragmented documentation and extra effort for developers.

Core Features & Use Cases

  • Standardized tables for screen inventories per actor, ensuring uniform data capture.
  • Flow diagram syntax for documenting user navigation paths with actions, success and error branches.
  • Presenter specification skeletons that define gateways, state, derived properties, actions, and TDD test outlines, ready to be adapted for each screen.
  • Use case: When the ui‑discovery agent produces raw screen lists, this skill formats them into ready‑to‑use markdown artifacts for downstream development and testing.

Quick Start

Invoke the ui-discovery-formats skill to generate the complete UI discovery document for the “Order Management” bounded context.

Frequently Asked Questions about ui-discovery-formats

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

FAQPage Schema
How do I generate standardized markdown templates for UI screen inventories?

To create user-flow diagrams for software documentation, apply a defined notation syntax that maps user navigation paths. This process documents actions alongside success and error branches, providing clear visual flow logic for development teams.

What is a presenter specification in UI discovery?

A presenter specification in UI discovery is a structured markdown skeleton defining gateways, state models, derived properties, and actions. It provides ready-to-adapt templates with TDD test outlines for individual screen development and testing.

How do I document user navigation paths with success and error branches?

Document user navigation paths by applying standardized flow diagram syntax that maps actions to success and error branches. This transforms raw UI discovery data into consistent markdown flow logic for downstream development.

Can I use markdown templates to create TDD test outlines for UI screens?

Yes, you can use markdown templates to create TDD test outlines by generating presenter specification skeletons. These skeletons include predefined actions, state models, and derived properties ready for adaptation into test-driven development templates.

Does UI discovery documentation require following specific naming conventions?

UI discovery documentation can require specific naming conventions, such as ensuring screen inventory tables follow French naming rules. This standardizes markdown artifacts for consistent data capture across different bounded contexts.