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

未關閉
#47 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
35/100
Issue 類型
文件
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
csharp, unity

研究方向

Start with the README and docs home, then review the repository settings for the social preview and the docs site's Open Graph image. Create the demo, Unity 6 before/after example, audience and comparison sections, and launch checklist; done means the README shows the demo and comparison above the fold, the social preview is set, and the checklist is complete.

由索引模型根據 Issue 內容生成。

描述

documentation marketing priority: medium

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.

主要語言
C#
星號
4
分支
0
PR 合併指標
30 天內沒有已合併 PR

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TMHSDigital/Unity-Developer-Tools 的其他 Issue

查看 TMHSDigital/Unity-Developer-Tools 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。