claw: visual_output.t27 -- a T27F visual in every output that did work (Closes #10508)

.claude/skills/t27f/SKILL.md

@@ -236,6 +236,22 @@ the specs', not repeated here.
    the session folder (`out-reels/`, gitignored, never `git add`).
 4. Anything not made: say which and why in the answer. Never show an older file as this turn's.
 
+## Visual in every output (Claude Code and TRI CLAW)
+
+**The rule is `specs/t27mcp/visual_output.t27`** (its `RULE_CLAUDE_CODE` and `RULE_TRI_CLAW` lines
+are what each host reads). **Its particle-still layer is `specs/claw/visual_output.t27`.** This
+section is the order of steps; which answer carries which visual and how it reaches each host are
+the specs', not repeated here.
+
+1. Decide the answer's kind (`K_*` in the t27mcp spec). A one-sentence reply or a question back
+   goes without a visual.
+2. Spec, flow or numbers: draw from t27f tool rows (`t27f_outline`, `t27f_graph`, `t27f_view`),
+   labelled, with the legend and the source file, as `answer_verdict` checks.
+3. A report of a piece of work: a particle still (`takes_still`). Render the reel on the Railway lab
+   (never the Mac), take the frame at `STILL_MS` with `ffmpeg -ss 9 -frames:v 1`, and bring it into
+   the session folder (`out-reels/`, gitignored, never `git add`).
+4. Anything not made: say which and why in the answer. Never show an older file as this turn's.
+
 ## Application: topic map (gHashTag/trinity#1677)
 
 Use this part when the user gives a topic or a client brief, not a spec.