generate-screen-inventory

Generate screen inventory Markdown files with YAML frontmatter and decision manifests.

3|Updated Jan 25, 2026

Search Tags:#ux design #markdown generation #screen inventory #scenario mapping #state modeling #decision manifest #deterministic design

Ready to run

npx skills add https://github.com/kapilvirenahuja/garura --skill generate-screen-inventory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-screen-inventory
Source: https://github.com/kapilvirenahuja/garura/tree/main/core/components/skills/generate-screen-inventory
Command: npx skills add https://github.com/kapilvirenahuja/garura --skill generate-screen-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It converts enriched capabilities, scenarios, and business rules into a complete set of screen inventory files so design and implementation can proceed deterministically.

Core Features & Use Cases

Stateful screen generation: Derives primary and supporting screens from success/failure scenarios and business rules, ensuring each screen includes at least three meaningful states (including an error-adjacent state).
Structured design-ready outputs: Writes one Markdown file per screen under the screens directory with the required section order and YAML frontmatter for downstream skills.
Decision surfacing traceability: Emits a decision-manifest.yaml that records inferred decisions with tiering and grounding references for orchestrated review.

Quick Start

Run generate-screen-inventory with the designer-provided contract paths (scope, enriched capabilities, epics, personas, product research, schema, and screens directory) to produce screen inventory Markdown files plus decision-manifest.yaml.

Frequently Asked Questions about generate-screen-inventory

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

FAQPage Schema

How do I generate a screen inventory from enriched capabilities and scenarios?▼

To generate a screen inventory, map success and failure scenarios into concrete UX screens with enumerated states. This process translates scope and research inputs into downstream-ready Markdown artifacts, writing one file per screen with YAML frontmatter and ordered sections.

What is state modeling for UX screens and when do I need it?▼

State modeling for UX screens derives primary and supporting screens from business rules, ensuring each includes at least three meaningful states including an error-adjacent state. You need it when translating scope and research inputs into deterministic, wireframe-ready design artifacts.

How do I create deterministic screen specs for wireframing and coverage validation?▼

Create deterministic screen specs by resolving required input paths against product_base and mapping capabilities into Markdown files with ordered sections. This enforces minimum state counts per screen without padding and records all inferred decisions into a decision-manifest.yaml for review.

Can I use scenario mapping to produce design-ready Markdown artifacts without manual state padding?▼

Yes, scenario mapping can derive screen inventories automatically by enforcing minimum state counts per screen without padding. It maps success and failure scenarios into structured Markdown files with YAML frontmatter, ensuring downstream wireframing and compilation proceed deterministically.

What inputs do I need for deterministic screen generation from capabilities?▼

Deterministic screen generation requires designer-provided contract paths including scope, enriched capabilities, epics, personas, product research, schema, and a screens directory. These inputs are resolved against product_base to produce screen inventory Markdown files plus a decision-manifest.yaml.

Why does screen inventory generation require an error-adjacent state for each screen?▼

Screen inventory generation requires an error-adjacent state to ensure each screen includes at least three meaningful states derived from failure scenarios. This prevents incomplete UX coverage and guarantees downstream wireframing and compilation address both successful and failed user interactions.