recipe-front-design

**Explicit User Instruction**: The user explicitly instructs and authorizes every subagent call named in this recipe. Execute each applicable call when its prerequisites are met. Execute Skill: documentation-criteria before document routing or creation. Execute Skill: llm-friendly-context before writing Agent prompts, handoffs, or generated artifacts. Execute Skill: subagents-orchestration-guide before invoking agents or resolving findings. Before the first finding disposition, read `references/review-resolution.md` from the loaded subagents-orchestration-guide skill. ## Outcome and Ownership Coordinate a Medium/Large frontend design from evidence to an applicable UI Spec and approved Design Doc. The orchestrator owns requirement convergence, Structural Scale, document routing, ADR qualification, evidence selection, and Review Resolution. Named specialists own semantic investigation and artifacts. The frontend Design Doc always carries the complete implementation design. An ADR batch narrows qualifying technical choices; an applicable UI Spec owns UI structure and behavior that remain to be designed. Requirements: $ARGUMENTS ## Flow ```text requirement source -> codebase-analyzer -> scope/document routing confirmation [Stop] | conditional UI analysis -> UI Spec review [Stop] | optional ADR batch/review [Stop] ...