code-writing-guide
SkillFiles & storageProvides coding guidelines for Unity projects. Make sure to use this skill whenever writing, creating, editing, or modifying code files. This includes implementing new features, fixing bugs, refactoring, adding tests, or any task that results in code changes. Even for small edits or one-line fixes, load this skill to ensure project conventions are followed.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the code-writing-guide skill
What this skill tells your AI
The instructions your AI receives, as published by nowsprinting/unity-coding-skills in skills/code-writing-guide/SKILL.md and read by ahel’s review.
Guide for writing code in Unity projects.
Rules
- Before modifying any code file, check if the editor is in Play Mode. If it is, stop it using the
unity_play_controltool first — Play Mode may skip recompilation, leaving stale code active. - When a change is a structural refactoring — renaming a symbol, extracting a method/interface/base class, changing a method signature, moving a type to another namespace, or deleting a symbol — use the Rider MCP refactoring tools (
rename_refactoring,extract_method,extract_interface,extract_base_class,change_api_signature,move_type_to_namespace,reorganize_namespaces,safe_delete) instead of text edits. They update all references and call sites across the solution. - Never create
.metafiles. Unity editor creates them automatically. - When editing (creating or modifying) scene (
.unity) or prefab (.prefab) files, use theedit-sceneskill. - When instantiating a prefab multiple times, give each instance a unique
GameObject.name; otherwise, automated tests cannot identify a specific instance. Use a concrete name (e.g.,"<PrefabName>(Hero)") or append an index (e.g.,"<PrefabName>(0)").
Resources
Read the appropriate resource file based on the situation:
- Before writing or modifying any code file: Read
${CLAUDE_SKILL_DIR}/resources/coding-guideline.md - Before writing or modifying any code file: Read
${CLAUDE_SKILL_DIR}/resources/unity-modern-guidelines.md - Before writing or modifying MonoBehaviour lifecycle or event-handling methods (Awake, Start, OnEnable, OnDisable, OnDestroy, Update, FixedUpdate, LateUpdate, OnCollision*, OnTrigger*, OnGUI, OnMouse*, OnBecame*, OnPreCull, OnPreRender, OnPostRender, OnRenderImage, OnRenderObject, OnWillRenderObject, OnAnimatorMove, OnAnimatorIK, OnDrawGizmos): Read
${CLAUDE_SKILL_DIR}/resources/unity-event-functions.md - Before referencing an API, verifying a package behavior, or looking up documentation: Read
${CLAUDE_SKILL_DIR}/resources/unity-references.md - When resolving diagnostics or handling code review feedback: Read
${CLAUDE_SKILL_DIR}/resources/diagnostics-review-feedback.md
Signals
- GitHub stars
- 21
- Forks
- 3
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
code-writing-guide- Source
- github.com/nowsprinting/unity-coding-skills