ijfw-ui-spec

# IJFW UI-Spec -- lock the visual contract before build Produce `.planning/<milestone>/<phase>/UI-SPEC.md` as the design contract for the active slice, then dispatch `ijfw-ui-auditor` as the final 6-pillar gate after implementation lands. Domain-agnostic. Same flow for: a web UI slice ("settings page"), a book chapter layout ("Ch4 spread + typography"), a campaign deck ("launch deck 8 slides"), a brand system ("v2 token refresh"). UI-SPEC.md is the visual counterpart to SPEC.md. ## When to fire 1. User explicitly asks: "ui spec", "design contract", "ui audit setup", "lock the design", or invokes `/ijfw-ui-spec`. 2. ijfw-workflow Deep path enters a frontend or visual-artifact build with no UI-SPEC.md present. 3. plan-phase is requested for a slice tagged `ui:*` or `visual:*` and no UI-SPEC.md exists. ## Process ### 1. Locate the active slice ```bash MILESTONE=$(cat .ijfw/state/active-milestone 2>/dev/null \ || ls -1 .planning/ | grep -E '^[0-9]' | tail -1) PHASE=$(cat .ijfw/state/active-phase 2>/dev/null || echo "$1") PHASE_DIR=".planning/${MILESTONE}/${PHASE}" MOCKUP_DIR="${PHASE_DIR}/mockups" mkdir -p "$PHASE_DIR" "$MOCKUP_DIR" ``` If `$PHASE` is unset and no argument supplied, ASK which slice to spec. Never guess. ### 2. Load context Read in order, skipping any that don't exist: 1. `.ijfw/memory/brief.md` -- the original ask 2. `DESIGN.md` -- existing design contract (root) 3. `.planning/<milestone>/<phase>/S...