agentsclimarketplace

Code writing guide

Skill nowsprinting/unity-coding-skills/skills/code-writing-guide

Skills and subagents for developing Unity projects with Claude Code — maintainable test design and implementation, test-first workflow, coding guidelines, scene editing, and more.

Install
npx -y skills add nowsprinting/unity-coding-skills --skill code-writing-guide

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Provides 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.

The file declares its own license as Unlicense. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, as published. Nobody here has run it

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_control tool first — Play Mode may skip recompilation, leaving stale code active.
  • Never create .meta files. Unity editor creates them automatically.
  • When editing (creating or modifying) scene (.unity) or prefab (.prefab) files, use the edit-scene skill.
  • 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

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.