game-new-project
Skill0 starsChanged 3 days agoMITView on GitHub
Scaffold a new Unity 6 mobile game (Android + iOS, 2D or 3D) with the cmpose generator, which runs on this machine as the cmpose MCP server (game_describe, game_generate). Use whenever the user wants to create / generate / scaffold a new game or Unity project — e.g. "bana bir oyun hazırla", "Unity oyun projesi oluştur", "3D bir mobil oyun kur", "create a 3D Unity game", "scaffold a 2D Unity game with leaderboards". When invoked the skill asks ONLY four fields — project name, app name, package, output directory — one at a time; everything else (template, render, flags, modules, theme) comes from the request or smart defaults and is NEVER asked. Then it generates the project locally, sets up git, verifies the Android APK and the iOS simulator build, and opens Unity.
In this repository20 other files it gives its agents.
- compass-kit/CLAUDE.mdCLAUDE.md
- unity-kit/CLAUDE.mdCLAUDE.md
- backend-new-projectSkill
- cmp-backendSkill
- cmp-code-rulesSkill
- cmp-commitSkill
- cmp-design-rulesSkill
- cmp-design-to-codeSkill
- cmp-detektSkill
- cmp-featureSkill
- cmp-gatesSkill
- cmp-maestroSkill
- cmp-new-projectSkill
- cmp-testingSkill
- cmp-verifySkill
- game-balanceSkill
- game-briefSkill
- game-lookSkill
- game-releaseSkill
- game-smokeSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Kept short: ONLY four fields are asked one at a time (project name, app name, package, output dir).
- Very specific: line 26
Run scripts with bash ~/.claude/skills/game-new-project/scripts/<name>.sh.
- Distinctive: line 40
Never generate any other way (no web API, no copying the template by hand).
- Very specific: line 42
Call game_describe once. It is the contract: unityVersion (the editor the project needs), template (the pinned repo + ref), defaults …
- Distinctive: line 47
Pre-fill from the request: if the user already named a field (project name, game title, package, folder), use it as that field's value and …
- Distinctive: line 83
Ask one question → wait → validate (below) → ask the next.
- Distinctive: line 120
Ask one yes/no ("Generate?
- Very specific: line 123
Call game_generate with projectName, appName, packageName, outputDir (absolute), templateType, render, minSdk, iosVersion, and for blank …
- Very specific: line 156
if defaults.autoBuildAndroid and doctor.androidModule: scripts/build-android.sh <projectDir> → OK: APK <path> (<size>) (about 8–10 min on …
- Very specific: line 161
When the builds are done (or skipped), if defaults.openUnity and doctor.unity is not null: open -a "<editor dir>/Unity.app" --args …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
game-new-project
Generate a Unity 6 mobile game with the cmpose generator. It runs on this machine as the cmpose MCP
server (@cmpose/mcp, tools game_describe and game_generate): no account, no API key, no upload.
Kept short: ONLY four fields are asked one at a time (project name, app name, package, output
dir); the template, render, flags, modules and theme come from the request and are shown
(changeable) at the confirmation step. Skill directory: ~/.claude/skills/game-new-project/.
Run scripts with bash ~/.claude/skills/game-new-project/scripts/<name>.sh.
There is no static contract copy: the rules are read from game_describe at run time.
0. MCP check + contract + preferences (silent)
- The cmpose MCP server must be connected. Its tools are
game_describeandgame_generate(usually listed asmcp__cmpose__game_describe/mcp__cmpose__game_generate). If they are not available in this session, stop before asking anything and tell the user, in their language:the generator runs locally as an MCP server; add it once with this command, then restart Claude Code (
/exit, thenclaude) and ask again:claude mcp add cmpose -- npx -y @cmpose/mcp@3.0.3- it needs Node.js 20+ and git: run
scripts/doctor.shand reportnode20andgit(if it cannot run, just say so). Never generate any other way (no web API, no copying the template by hand).
- Read
defaults.json(prefs). - Call
game_describeonce. It is the contract:unityVersion(the editor the project needs),template(the pinnedrepo+ref),defaults(templateType,render,flags,minSdk,iosVersion),themes(default,familieswithid,title,suits,fontPairs) andcontract(templateTypes,renders,flags,flagRequires,idGroups,limits,reservedNames,reservedModuleNames,reservedPackagePrefix). - Pre-fill from the request: if the user already named a field (project name, game title, package, folder), use it as that field's value and skip that question in step 2.
1. Auto-defaults — DO NOT ASK these (keep the form short)
- Template →
showcase(the sample games with every flag on). Useblankonly when the user asks for an empty game ("boş", "blank", "sıfırdan", "örnek oyunsuz", "from scratch") or names a specific set of flags or modules to start from. - Render →
defaults.render(2d);3dwhen the request says "3D", "3d", "üç boyutlu" or "three-dimensional". - Flags (blank only) → the request's wording matched to
contract.flags(save system, UI theme, languages / çoklu dil, network, network inspector, leaderboards / skor tablosu, crash reports / crashlytics / analytics / çökme raporu / analitik →insights, …). The generator adds the required ones (flagRequires, e.g.networkInspector ⇒ network); never pass flags withshowcase. Turn onpurchases/adsonly when the user explicitly asks for in-app purchases / a paywall (RevenueCat) or for ads (AdMob). Never infer them from words like "premium", "subscription", "purchases" or "satın alma" alone (a "premium-feeling puzzle game" is not a purchases request); if unsure, leave them off and ask on the confirmation screen (step 3). Turn oninsights(Firebase Crashlytics + Analytics) only when the user asks for crash reports or analytics; showcase has it. It stays off in the game until the user adds the Firebase config files (the generator's warning says which). - Features (blank only) → module names the request names (lower case,
limits.moduleNameMaxcharacters, at mostlimits.maxModules, not inreservedModuleNames); none otherwise. - Theme → the family of
themes.familieswhosesuitsfits the game the user describes; none (the template default) when nothing fits orthemes.familiesis empty. Passprimary/accentonly when the user names colours (#RRGGBB). - Company name → never passed: the generator takes the package's second segment, capitalized
(
com.example.skyhopper→Example). It becomes the C# namespace<Company>.<Project>; show it. - IDs → never asked: the test IDs / placeholders stay (
idGroups: AdMob, RevenueCat, game services); the generator reports each as a warning. - Min SDK / iOS →
defaults.minSdk/defaults.iosVersion, withinlimits(minSdkMin–minSdkMax,iosVersionMin–iosVersionMax). - Template → the pinned
templateofgame_describe. Never passtemplateRefunless the user asks for a specific tag.
2. Ask ONLY these four — ONE at a time, in order
Ask one question → wait → validate (below) → ask the next. Don't batch. Ask nothing beyond these four. Skip any the user already gave in their request.
- Project Name — letters or digits, starting with a letter, no spaces, up to
limits.nameMax(e.g.SkyHopper). Becomes the folder, the C# namespace and the APK name; not one ofreservedNames. - App Name — the title on the home screen (e.g.
Sky Hopper), up tolimits.appNameMax. Offer the project name split into words as the default. - Package Name — offer the saved
packagePrefixand the project name in lower case ("I'll build it ascom.example.<projectname>"), or let them type the full package. Lower case, at least 3 segments, up tolimits.packageNameMax, no keyword segment, not underreservedPackagePrefix. Its second segment becomes the company name. - Output directory — the parent folder: default
{outputDir}; the project is created at<outputDir>/<projectName>. Show the resolved absolute path (expand~:game_generateneeds an absoluteoutputDir).<outputDir>/<projectName>must not exist or must be empty.
Validate each answer immediately
Apply the game_describe rules. If invalid, re-ask that same field with the reason; don't advance
until valid (cap ~2 re-asks). game_generate's error is the final authority.
3. Confirm with an anatomy preview
Show a one-screen summary and a project tree, for example:
SkyHopper/ ← /abs/output/SkyHopper
├── Assets/
│ ├── Editor/Build/BuildScript.cs Example.SkyHopper.Editor.Build (batch builds)
│ ├── Scenes/ Boot scene first
│ └── … showcase: the sample games; blank: Sample + your modules
├── Packages/ ProjectSettings/ Unity <unityVersion>
├── .cmpose/generation.json the generation record
└── README.md signing, IDs, release checklistThen the values: project, app name, package, company (namespace <Company>.<Project>), path,
template (showcase/blank), render (2d/3d), flags and modules (blank), theme — from the request,
changeable here, Min SDK, iOS, the Unity version (unityVersion) and the template (repo@ref).
Ask one yes/no ("Generate? — or tell me what to change").
4. Generate
Call game_generate with projectName, appName, packageName, outputDir (absolute),
templateType, render, minSdk, iosVersion, and for blank flags / features, plus theme
when one was picked. Never ids, companyName or templateRef (unless asked).
- success →
structuredContent.projectDiris the project; show eachwarningsentry verbatim; continue. - error result → its text is the reason:
| error text | action |
projectName … / appName … / packageName … / companyName … is derived from packageName's second segment … | re-ask that field (the package for companyName) with the message, retry once |
features entry "…" … / features allows at most … | drop or rename that module (say so), retry once |
outputDir must be an absolute path … | expand ~ / resolve the path, retry once |
… already exists and is not empty / … is a file | ask for another output directory or project name, retry once |
Could not download the template … (the first run downloads it) | ask the user to check the connection, retry once |
anything else (Generation failed: …) | show it and stop |
Generation is local: there is no rate limit; never loop on the same error.
5. Setup
scripts/setup.sh <projectDir> → git init + initial commit (OK: git); a project that is already
a repository is left as is. The template ships the Unity .gitignore.
6. Verify + open Unity (capability-aware, background)
Run scripts/doctor.sh "<unityVersion>" once →
{"node20","git","unity","androidModule","iosModule","xcode","iosSimSdk","pod"}.
doctor.unitynull → the editor of that version is not installed: say so in one line (install Unity<unityVersion>in Unity Hub with the Android and iOS Build Support modules, or setUNITY_EDITOR), skip the builds and the opening.- A batch build cannot run while the editor has the project open (the project lock), so the order is: builds first, then open. If the user wants the project open right away, skip the builds and say so ("the builds are skipped because Unity has the project open").
- Otherwise run in the background, one after the other (Unity cannot build one project twice at
the same time), as a single background command:
- if
defaults.autoBuildAndroidanddoctor.androidModule:scripts/build-android.sh <projectDir>→OK: APK <path> (<size>)(about 8–10 min on the first import); - then, if
defaults.autoBuildIosanddoctor.iosModule,doctor.xcodeanddoctor.iosSimSdk:scripts/build-ios.sh <projectDir>→OK: iOS simulator build. Tell the user they run and continue with step 7; report each line as it arrives.
- if
- When the builds are done (or skipped), if
defaults.openUnityanddoctor.unityis not null:open -a "<editor dir>/Unity.app" --args -projectPath "<projectDir>"(<editor dir>isdoctor.unitywithout/Unity.app/Contents/MacOS/Unity). - A missing capability → say so in one line and skip (no Android module / iOS module: add it in
Unity Hub; no full Xcode or no simulator SDK: install it; no
podwith a Podfile: install CocoaPods). Never fail the whole flow; aSKIP:line is not an error. - A
FAIL:from a build on a freshly generated project is a generator/template defect, not the user's code: show the lines and say so; do not patch the project. An environment error in those lines (a download, a licence, a lock file, the time limit) is not a defect: show it and say what to fix. The logs are in<projectDir>/Builds/logs/. - The game is not launched on an emulator or a simulator.
7. Report + remember
Summarize:
- the absolute project path, the template (
repo@ref), the template type, render, theme and, for blank, the flags and modules; - the warnings verbatim, and: the project keeps the test IDs (AdMob test ads, the RevenueCat Test
Store key, placeholder leaderboard IDs); enter your real IDs before release (
README.mdof the project: signing, IDs, release checklist); - how to open and run it: Unity Hub → Add → the project folder, editor
<unityVersion>(Android and iOS Build Support); press Play in the Boot scene, or build with File > Build Profiles; - the build results as they arrive.
Offer to persist any changed preferences (
packagePrefix,outputDir,render,minSdk,iosVersion,openUnity,autoBuildAndroid,autoBuildIos) back todefaults.json.
Notes
- The first generation downloads the pinned template into
~/.cache/cmpose(CMPOSE_CACHE_DIRoverrides it); later runs are offline. - A generated project is only as correct as the pinned template of the installed
@cmpose/mcp; to get a newer template, install a newer MCP version. - The builds stop after
UNITY_BUILD_TIMEOUTseconds per step (default 1800). - The install command above must stay identical to
cmp-new-project's (scripts/check-skills.shchecks it).
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.

