Unity Gamedev Skill Pack

Name: Unity Gamedev Skill Pack
Author: akillness

akillness/oh-my-skills

153 installs
40 repo stars
Updated August 4, 2026
akillness/oh-my-skills

Implement Unity gameplay, scenes, scripts, input, UI, and common gamedev patterns while keeping project structure and C# conventions consistent across a playable build.

About

unity-gamedev-skill-pack from akillness/oh-my-skills bundles Claude guidance for Unity game development, covering scripting, scenes, gameplay systems, and client-side patterns. It targets developers building or extending Unity titles who want consistent C# and editor workflows during active implementation.

Unity project and C# scripting guidance
Scene, component, and gameplay workflow patterns
Input, UI, and iteration-friendly structure
Mobile and desktop game build alignment
Reusable gamedev conventions in one pack

Unity Gamedev Skill Pack by the numbers

153 all-time installs (skills.sh)
Ranked #110 of 247 Game Development skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

npx skills add https://github.com/akillness/oh-my-skills --skill unity-gamedev-skill-pack

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/akillness/oh-my-skills/unity-gamedev-skill-pack.svg)](https://skillselion.com/skills/akillness/oh-my-skills/unity-gamedev-skill-pack)

Installs	153
repo stars	★ 40
Last updated	August 4, 2026
Repository	akillness/oh-my-skills ↗

What it does

Implement Unity gameplay, scenes, scripts, input, UI, and common gamedev patterns while keeping project structure and C# conventions consistent across a playable build.

Files

SKILL.mdMarkdownGitHub ↗

Unity GameDev Skill Pack

Use this skill to turn an external Unity skill pack into a reviewed internal package.

When to use this skill

You discovered an external Unity skill repository during survey runs.
You want selective reuse (workflow ideas) rather than direct copy-paste.
You need PR-safe imports with risk notes, provenance, and rollback.

When not to use

You need to debug a concrete Unity runtime/build error right now.
You are writing gameplay code directly instead of curating skill docs.

Instructions

Step 1: Capture source provenance

Record at least one concrete source URL plus retrieval method (indexed snippet or direct page retrieval).

Step 2: Extract reusable patterns only

From the source pack, keep transferable workflow units (setup checks, guardrails, validation order). Drop tool-locked fluff and unverifiable claims.

Step 3: Run safety gates

Before adding any imported guidance:

verify license suitability
check recency/activity
check that instructions are deterministic and non-destructive
flag engine-version assumptions explicitly

Step 4: Package into local skill structure

Create/update:

SKILL.md (operator-facing workflow)
SKILL.toon (compact behavior contract)
evals/evals.json (prompt assertions that enforce boundaries)

Step 5: Add risk + rollback in PR

State what was imported, what was intentionally excluded, known risks, and exact rollback path (revert commit/PR).

Step 6: Validate before merge

Run JSON checks, diff hygiene (git diff --check), and skill validator scripts when available.

Output format

Return a short curation packet:

Source(s)
Imported patterns
Excluded patterns
Risks
Validation results

Examples

"Survey found tjboudreaux/cc-plugin-unity-gamedev; import only reusable setup/validation flow into local skill docs with risk notes."
"Source license unclear after metadata fallback" -> keep as discovery evidence but do not promote/import without explicit exception rationale.

Best practices

1. Prefer adaptation over replication: rewrite external guidance in local conventions. 2. Keep provenance labels near claims so reviewers can verify quickly. 3. Always include rollback steps in PR body when importing external workflows.

References

https://github.com/tjboudreaux/cc-plugin-unity-gamedev

{
  "skill_name": "unity-gamedev-skill-pack",
  "evals": [
    {
      "id": 1,
      "prompt": "we found tjboudreaux/cc-plugin-unity-gamedev in the hourly survey. add it to our repo safely",
      "expected_output": "A provenance-first curation flow that evaluates license/recency/safety before adapting reusable Unity workflow patterns into local skill files.",
      "assertions": [
        "Mentions provenance capture with source URL and evidence label",
        "Checks license and recency before import",
        "Describes selective adaptation instead of blind copy"
      ]
    },
    {
      "id": 2,
      "prompt": "copy all prompts from this external unity repo directly into our skills and merge quickly",
      "expected_output": "A refusal of blind copy with redirection to safety gates and PR-visible risk/rollback documentation.",
      "assertions": [
        "Rejects blind direct-copy behavior",
        "Requires risk and rollback notes in PR output",
        "Requires validation before merge"
      ]
    },
    {
      "id": 3,
      "prompt": "prepare a merge-ready update for imported unity workflows",
      "expected_output": "A package that includes SKILL.md, SKILL.toon, evals, and validation checkpoints.",
      "assertions": [
        "Includes local package structure (SKILL.md, SKILL.toon, evals/evals.json)",
        "Includes validation steps such as git diff --check or JSON validation",
        "Includes explicit rollback path"
      ]
    }
  ]
}

N:unity-gamedev-skill-pack
D:Evaluate and adopt Unity game-development skill packs from external repositories into a safe reusable local package with provenance risk controls and rollback.
G:unity game-development skill-curation claude-code repository-maintenance
U[5]:
  Curate external Unity skill packs discovered via survey runs
  Reuse only transferable workflow patterns and guardrails
  Enforce license recency and deterministic-instruction checks
  Package updates as SKILL.md SKILL.toon and evals/evals.json
  Require PR-visible risk and rollback notes before merge
S[6]{n,action,details}:
  1,Capture provenance,Record source URLs and evidence labels before adaptation
  2,Extract patterns,Keep reusable workflow units and drop unverifiable claims
  3,Run safety gates,Check license recency determinism and version assumptions
  4,Package locally,Write SKILL.md SKILL.toon and evals for the curated workflow
  5,Document risk and rollback,Include imported/excluded scope plus revert plan in PR
  6,Validate,Run JSON check diff hygiene and available skill validators before merge
R[5]:
  Do not blindly copy third-party prompts into internal skills
  Do not import workflows without license and recency checks
  Keep destructive or environment-specific commands behind explicit warnings
  Keep provenance labels explicit for every imported claim
  Do not merge when validation gates fail
E[2]{desc,in,out}:
  "Survey-derived import","we found a Unity skill-pack repo in hourly survey candidates and need a safe internal adaptation","Produces provenance-first curation packet with imported/excluded patterns risk notes and validation status"
  "Risky direct-copy request","just copy this external Unity prompt pack into our repo","Refuses blind copy and reroutes to gated curation steps with license/recency checks"