claude-skills

Executes a coding plan. Receives an explicit plan (file paths, changes, scope) and applies it, strictly following the project's coding principles. Does not re-plan, expand scope, or refactor unrelated code. Use after a planner has produced a concrete plan — delegate to this agent to perform the actual edits.

Performs disciplined web research with source-cited reporting. Prefers primary sources (official docs, RFCs, source code, standards bodies, academic papers) over secondary (recognized expert blogs) over tertiary (Stack Overflow, Reddit, AI summaries). Every factual claim cites the source it came from; anything not directly sourced is flagged as an inference. Use when the user asks to research a topic, gather information from the web, compile findings, verify a technical claim, or "what does X say about Y". Refuses to assert facts it cannot cite.

A concise, opinionated reference of C# / Unity / general engineering principles to follow when writing or reviewing code (readonly defaults, no-comment-if-code-explains, no LINQ in hot paths, server-authoritative networking, scale-aware design, anti-patterns to refuse). Use when the user asks about coding standards, style guide, best practices, how to write idiomatic C#, or "what rules should I follow here". Loaded automatically by the `coder` agent.

Generates a concise PR description for the current branch using a Why / What / Tested / Demo template (Conventional Commits title, auto-linked issues, UI-aware demo section). Use whenever the user asks to write a PR description, draft a PR, open a pull request, create a PR, summarize a branch for review, or asks "what should this PR say".

Builds the current Unity project from the command line for a target platform (Windows, Mac, WebGL, iOS, Android, Linux). Creates Assets/Editor/BuildScript.cs if it doesn't exist, invokes Unity in batch mode via -executeMethod, and reports build success or failure with the artifact path. Use when the user asks to build the Unity project, compile for Windows/Mac/WebGL/iOS/Android, do a release build, do a CI build, or "make a build".

Sets up Unity's Multiplayer Play Mode (MPPM) in the current project so the dev can test up to 4 instances at once from a single Editor — ideal for card games like Guandan. Installs the MPPM package, writes a Player Tag-aware bootstrap that auto-starts Host vs Client on Play (detects Mirror or Netcode for GameObjects), and documents the virtual-player setup. Use whenever the user asks to set up local multiplayer testing, run multiple Unity instances, test multiplayer locally, spin up multiple clients, set up MPPM, or test the game without separate machines.

Scaffolds a new empty Unity project at a given path via the command-line Editor, then patches Packages/manifest.json to add a render pipeline (URP / HDRP) and common dev packages (Input System, Test Framework). Use when the user asks to create a new Unity project, scaffold a Unity game, start a new Unity codebase, bootstrap a Unity project, or initialize a fresh Unity project.