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

user/agents/skills/frontend-design/SKILL.md

@@ -64,7 +64,11 @@ This is the rule from my preferences, spelled out:
    way in one sentence, they are the same mock.
 2. Build them as static pages. Real content, not grey boxes labelled "image here", because
    the content is where most of the design decisions turn out to matter.
-3. Publish them with a simple http server, report the URL, and stop.
+3. Show them, and stop. In T3 Code, render each direction in the thread with `html_preview`
+   then `html_render`, one direction per render so each expands full screen on its own, and
+   link the files by absolute path for the file viewer. `html_render` overrides a page
+   background, so a direction that paints its own goes inside an `<iframe srcdoc>`. Outside
+   T3, publish them with a simple http server and report the URL.
 4. Wait for a decision before implementing anything in real components.
 
 Do not edit real components first. Do not keep polishing past the point where a choice