README and landing: demo GIF, before/after Unity 6 output, social preview, launch plan #47

Why it matters

A first-time visitor sees a long list of counts (18 skills, 8 rules, 20 snippets...) but no evidence of what the tool does in practice, and no reason to choose it over the model alone or other Unity AI tools. The repo has 4 stars and 0 forks, so presentation is the cheapest growth lever.

Suggested improvements

• Show, don't count: a 20-30 second GIF or video at the top of README and the docs home: ask for a dissolve shader or a player controller, see the tool call and the result.
• Before/after: one side-by-side of default AI output (e.g. FindObjectOfType, rb.velocity, CGPROGRAM in URP) vs. output with this plugin. This is the clearest value proposition: "AI that writes Unity 6 code, not Unity 2019 code".
• Lead with the pitch in one sentence, then install, then features; move counts lower.
• Social preview image (repo Settings > Social preview) and an Open Graph image for the docs site.
• Who it's for section: solo indies, students, teams adopting Unity 6.
• Comparison table vs. "plain Cursor" and vs. editor-bridge MCP servers (complementary).
• Add the missing GitHub topics claude-code, unity6, ai-assistant.
• Launch posts once install is one command: r/Unity3D, r/gamedev, Unity Discussions, Cursor forum, MCP directories.

Done when

README has a demo and a before/after section above the fold, the social preview is set, and a launch checklist is completed.