ui-brief-generator

Consolidate scattered UI specifications by synthesizing docs, task shards, and reference images into a single executable UI brief. This reduces ambiguity and speeds up project kickoff by structuring family, content contracts, and smoke routes for downstream execution.

A task shard is a metadata-ready output generated alongside a design brief to support cross-team handoffs. It structures specific UI tasks for engineering execution, ensuring that visual assets and screen specifications are actionable and trackable.

Generate a task-ready brief by providing a screenId, taskId, or specification path. The system synthesizes these inputs with reference images and summary docs to produce structured briefs containing skin fragments and smoke routes for immediate handoff.

Yes, you can use a screenId or taskId to update existing UI briefs as source materials evolve. This input flexibility allows you to refresh the synthesized design documentation and task shard metadata without regenerating the entire specification from scratch.

Structure UI specs for early design sprints by consolidating them into a formal brief with family, content_contract, and skin fragments. This approach transforms scattered visual assets and summary docs into actionable smoke routes and references for rapid execution.

Consolidation depends on the structure of cross-reference-index files and summary docs; disorganized inputs may limit the accuracy of generated skin fragments and smoke routes. Ensure screenId and taskId mappings are clear to maintain brief integrity.