ui-family-architect

You assign structural families by providing a proof draft path, which the workflow reads to map each visual zone to a structural family, a theme stack, and a recipe seed, generating a ready-to-use family-map for downstream pipeline steps.

A UI family-map allocates structural families and theme stacks to visual zones. You need it after proof draft creation and reference decomposition to validate family availability before feeding recipe seeds to the recipe compiler.

Yes, you can pass an optional themeOverride parameter when initiating the workflow to replace the default theme stack configuration for the target screen's visual zones during family assignment.

The workflow validates the existence of required structural and skin families, actively flagging missing asset or recipe gaps and capturing unresolved questions for follow-up in the output family-map.

Yes, ui-reference-decompose is a prerequisite pipeline step. You must decompose references first to generate the proof draft input required to assign structural families and theme stacks to each visual zone.

The best way to generate recipe seeds is to use a proof draft to assign structural families and theme stacks, which outputs prefilled recipe fields that directly accelerate the subsequent recipe compiler and UI vibe pipeline.