lfe-visual-check

LFE Visual Check — Render, Reason, Hand the Verdict to the Human

Position in Pipeline

• Phase: 3 (Inspector sub-skill)
• Persona: Inspector (read-only; writes only .plans/checks/)
• Trigger: Invoked by /lfe-inspector Sub-Skill Dispatch when armed — either lfe-visual-check: true in .docs/quality/inspector-config.md / ## Inspector Overrides, or the Visual Floor auto-arms it because the slice's changed files touch a visual file class (the floor is a minimum; an override leaves it armed).
• Output: .plans/checks/visual_findings.md — aggregated by the Inspector into critique.md, and the basis for the human visual sign-off at the finalization gate.

Mission

Give the Inspector eyes. Render the changed UI surface, reason over what it shows, and present it to the human for a visual verdict. The Inspector asserts the technical pass on its own authority; the visual verdict belongs to the human alone. This sub-skill renders and presents — the human alone declares whether it looks right.

Hard Rules

1. Dispatch Context Required (refuse direct invocation): This skill is dispatched by /lfe-inspector Step 6 — it is not a Brain-typeable skill (per LLM_AGENT_GUIDE.md §8.8 Skill Invocation Authority). If invoked without .plans/builder_done.md for the current slice, halt immediately and reply: "/lfe-visual-check is an Inspector sub-skill dispatched by /lfe-inspector. It cannot be run standalone. Run /lfe-inspector — the dispatcher will invoke this sub-skill if it is armed in .docs/quality/inspector-config.md (or via an ## Inspector Overrides section in active_plan.md), or auto-armed by the Visual Floor." Direct invocation produces orphaned findings files and breaks the Inspector's aggregation logic.
2. Artifact-free: Reason over the in-context render and write prose only. This skill saves no image files — keeping the blank-canvas seal intact and the run self-cleaning. (Render tools return the pixels in-context; capture the reasoning, leave the bytes unsaved.)
3. Render-then-reason: Findings come from looking at the rendered surface, cited concretely (what element, what looks wrong).
4. Defer the verdict: Write the findings and a human-action instruction; the human declares the visual verdict at the finalization gate. This skill records no visual_confirmed / visual_signoff itself — that is the Inspector's finalization act, taken on the human's word.
5. Diff-scoped: Reason about the visual file classes changed in builder_done.md; skip unrelated surfaces.