generate-wireframes

Generating wireframes from markdown screen specifications involves reading existing screen inventory files, resolving paths against the product base, and appending ASCII box-drawing wireframe sections with state-by-state component placement directly into the markdown.

A state-driven UI layout spec defines concrete grid and region placements, component inventories, and interaction patterns for each enumerated state in a screen file. You need it when bridging high-level screen definitions to buildable UI layouts during the design stage.

Yes, markdown can be used to create low-fidelity wireframes by appending non-visual ASCII box-drawing sections that show component placement and per-state layout structure, transforming screen inventories into visual-first wireframe content.

Documenting UI layout decisions for intent-driven development requires generating a decision-manifest.yaml file that captures inferred layout choices tiered by grounding, allowing orchestrators to surface resolved decisions after wireframe generation completes.

Yes, this wireframe generation approach works without external dependencies, relying solely on existing markdown screen files, product research paths for capability tradeoffs, and a decision manifest path passed from the calling agent's JSON contract.

Limitations of generating ASCII wireframes inside markdown files include producing only low-fidelity, non-visual representations rather than rendered mockups, and requiring resolved input paths alongside product research data to properly infer layout rules and grid definitions.