What problem does it solve?
This Skill solves the problem of documenting a legacy system’s user interface when you cannot (or do not want to) run the system, by turning screenshots into a structured map of screens, components, navigation flows, and states.
Core Features & Use Cases
- Screenshot-driven UI documentation: Inventories each provided screen with its purpose, state (loading/empty/filled/error/confirmation), and user entry context.
- Component extraction: Identifies forms (fields, validations, buttons), tables/listings (columns, per-row actions, filters/pagination), navigation elements (menus, breadcrumbs, links), and feedback mechanisms (messages, modals, tooltips).
- Navigation and state mapping: Produces navigation flow relationships across screens and distinguishes the same screen in different states; maps each screen to the appropriate unit using the configured granularity and feature/module/endpoints.
- Output organization for discovery: Saves per-unit screenshots and generates
screens.md plus global inventory.md and a Mermaid flow.md that links units.
Quick Start
Send screenshots of the system screens you want documented (start with the main screens and key navigation flows).