Show mocks in T3 Code threads, and drop the t3 MCP servers that T3 already provides

user/agents/skills/grilling/SKILL.md

@@ -121,8 +121,8 @@ Announce the path, then create a todo per item and work them in order.
   immediately rather than spending a round on the details of something that needs splitting first.
   Each sub-project earns its own design cycle.
 - **Visual questions get mocks, not prose.** Where the open question is what something should look
-  like, stop describing it: build several distinct static mocks, serve them, report the URL, and wait
-  for a pick. Never edit a real component to answer a layout question.
+  like, stop describing it: build several distinct static mocks, show them in the thread (or serve
+  them and report the URL outside T3 Code), and wait for a pick. Never edit a real component to answer a layout question.
 
 ## The written spec (architectural only)