unity6-project
Skill0 starsChanged 6 months agoMITView on GitHub
Unity 6 项目开发规则。Use when working on Unity 6 projects, Unity C# scripts, AI gameplay prototypes, NavMesh, Behavior/behavior trees, ML-Agents, Sentis/ONNX inference, Unity package setup, scenes, prefabs, tests, or Unity validation instructions.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-config-maintainerSkill
- coderSkill
- engineer-coder-orchestratorSkill
- engineerSkill
- github-repo-standardsSkill
- learning-blogSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read only what is needed:
- Very specific: line 30
Use [SerializeField] private for Inspector parameters.
- Distinctive: line 32
Put AI tuning values such as radius, speed, cooldown, and layer masks in Inspector.
- Distinctive: line 33
Verify package names and versions from Package Manager, local manifest, or official docs.
- Very specific: line 34
Do not commit Library/, Temp/, Logs/, training outputs, large generated assets, or user local settings.
- Distinctive: line 35
Use Git LFS before committing large binary assets that must be versioned.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Unity 6 Project
First Reads
Read only what is needed:
CLAUDE.mdfor project rules.README.mdfor setup and current scope.ProjectSettings/ProjectVersion.txtfor Unity version.Packages/manifest.jsonwhen packages are involved.- project planning docs when milestones or learning goals matter.
Workflow
- Identify the active milestone or gameplay goal.
- State the smallest useful next step and acceptance check.
- Make scoped changes under the existing Unity project root.
- For scripts, prefer
Assets/_Project/Scripts/or the local project convention. - For tests, prefer
Assets/_Project/Tests/or the local project convention. - Explain Unity validation steps: scene, GameObject, components, Inspector values, Play/Test Runner checks.
Rules
- Communicate in Chinese; keep C# identifiers in English.
- Use
[SerializeField] privatefor Inspector parameters. - Cache component references; avoid expensive lookup in
Update(). - Put AI tuning values such as radius, speed, cooldown, and layer masks in Inspector.
- Verify package names and versions from Package Manager, local manifest, or official docs.
- Do not commit
Library/,Temp/,Logs/, training outputs, large generated assets, or user local settings. - Use Git LFS before committing large binary assets that must be versioned.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

