Skip to content
Skills Library
Programming · Building & coding

farhat-unity-builder

/farhat-unity-builder

Builds the story-driven 3D action-adventure game "Farhat: The Prince of the Desert" (52 chapters, two seasons) in Unity 6 from the production bible. Use when asked to create, extend, test, fix, package or release the Farhat game, to set up its Unity project and MCP connectors, to generate or replace chapter scenes, to download and license-check 3D assets, textures, HDRIs or audio for it, or to run its episode check, QA, CI or release steps. Covers the full pipeline from an empty folder to a playable greybox of all 52 chapters, then chapter-by-chapter production to release.

Repository
farhat ↗
Licence
MIT
Last repository change
08.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
145
Scripts
83
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 83 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/_common.py, scripts/asset_fetch.py, scripts/blender_gltf_to_fbx.py, scripts/check_env.py, scripts/ledger.py, scripts/license_ledger.py, scripts/progress.py, scripts/scaffold_project.py

What it does and when to use it

Builds the story-driven 3D action-adventure game "Farhat: The Prince of the Desert" (52 chapters, two seasons) in Unity 6 from the production bible. Use when asked to create, extend, test, fix, package or release the Farhat game, to set up its Unity project and MCP connectors, to generate or replace chapter scenes, to download and license-check 3D assets, textures, HDRIs or audio for it, or to run its episode check, QA, CI or release steps. Covers the full pipeline from an empty folder to a playable greybox of all 52 chapters, then chapter-by-chapter production to release.

Triggers from the description

Farhat: The Prince of the Desert
Original author description

Builds the story-driven 3D action-adventure game "Farhat: The Prince of the Desert" (52 chapters, two seasons) in Unity 6 from the production bible. Use when asked to create, extend, test, fix, package or release the Farhat game, to set up its Unity project and MCP connectors, to generate or replace chapter scenes, to download and license-check 3D assets, textures, HDRIs or audio for it, or to run its episode check, QA, CI or release steps. Covers the full pipeline from an empty folder to a playable greybox of all 52 chapters, then chapter-by-chapter production to release.

How it works

  1. What exists, and what does not
  2. Step 0: confirm the basics (2 minutes)
  3. Where every fact lives
  4. Non-negotiable rules
  5. The pipeline
  6. Using the connectors
  7. When to stop and ask the human
  8. Reporting
  9. File map
Original SKILL.md headings · 147 lines, 1,686 words
SKILL.md preview
---
name: farhat-unity-builder
description: Builds the story-driven 3D action-adventure game "Farhat: The Prince of the Desert" (52 chapters, two seasons) in Unity 6 from the production bible. Use when asked to create, extend, test, fix, package or release the Farhat game, to set up its Unity project and MCP connectors, to generate or replace chapter scenes, to download and license-check 3D assets, textures, HDRIs or audio for it, or to run its episode check, QA, CI or release steps. Covers the full pipeline from an empty folder to a playable greybox of all 52 chapters, then chapter-by-chapter production to release.
---

# Farhat Unity Builder

You are building one specific game from a finished design. The design is in this skill, the code foundation is in this skill, and the
tools to verify your work are in this skill. Your job is to run the pipeline in order, prove each step with a command, and stop at
the human gates. Do not improvise story, do not skip verification.

## What exists, and what does not

| Exists in this skill | Does not exist, and you must not pretend it does |
| --- | --- |
| The full bible and project document (`references/bible/`, `references/project/`) | Episode footage. You cannot watch episodes. Unverified chapters stay `Inferred` until a human confirms them |
| `data/chapters.json`: all 52 chapters with objectives, checkpoints, failure rules, unlocks, spec text and verification tags | Final character art. Characters are modelled from the rights holder's model sheets; use the stand-in rigs until then |
| A compile-checked Unity C# foundation (`templates/unity/`): core, data, save, systems, story flow, UI, editor tools, tests | A Unity licence or store accounts. The human activates Unity and owns Steam or console accounts |
| Scripts that validate data, fetch licensed assets, drive Unity in batch mode, scaffold the project and track progress | Voice, music and final localisation. These need the rights holder's permission and a human |
| A generator that builds a playable greybox scene for every chapter | A guarantee of fun. Playtests with people decide that |

## Step 0: confirm the basics (2 minutes)

1. Run `python3 scripts/check_env.py`. Required: Python 3.9+, Git, Unity 6.3 LTS. If Unity is missing, tell the human to install it through Unity Hub and activate a licence, then stop. Never try to work around a missing editor.
2. Run `python3 scripts/validate_chapters.py` and `python3 -m unittest discover -s tests`. Both must pass before you touch anything. If they fail, the skill is damaged: report it, do not continue.
3. Ask the human once, in one message: (a) where the game project should live, (b) confirmation that they hold the licence for the series (the project owner stated this; ask for it to be confirmed in writing before any release), (c) whether to use the English names (Egokhan, Rashid) or the alternate dub names. Default to English names if they do not answer.

## Where every fact lives

| You need | Read |
| --- | --- |
| Story, characters, names, tone | `references/bible/03-story-bible.md`, `references/bible/04-characters.md` |
| One chapter's beats, level, mechanics, fail states, unlocks | `data/chapters.json` (field `spec`), and `references/bible/10-season-1-chapters-part-one.md` or `references/bible/11-season-2-chapters-part-two.md` |
| Mechanics: combat, light meter, Shadow, alchemy, decode, vehicles | `references/bible/06-core-gameplay-systems-all-g.md` |
| What counts as failing, difficulty, accessibility | `references/bible/07-failure-rules.md`, `references/bible/08-difficulty-accessibility-and-audience-safety.md` |
| Bosses, fragments, unlock timeline, art, audio, interface | `references/bible/12-boss-and-set-piece-list.md`, `13-progression-and-fragment-tracker.md`, `14-art-audio-and-interface-direction.md` |
| Architecture, stack, pipeline, code standards | `references/project/05-system-architecture.md` to `08-content-pipeline-and-tooling.md` |
| Testing, performance budgets, troubleshooting, deployment | `references/project/09-quality-assurance-and-testing.md` to `12-deployment-and-release.md` |
| How to operate (rules, gates, commands) | `references/00-agent-playbook.md` and the files `01` to `08` listed at the end of this file |

Read the playbook (`references/00-agent-playbook.md`) before the first build step. It is short and it contains the rules you are
most likely to break.

## Non-negotiable rules

1. **Story facts come only from the bible and `data/chapters.json`.** If a fact is not there, you do not know it. Never fill a gap from memory of the series. Mark the gap and ask.
2. **Tags are law.** `Verified` chapters can be locked. `Inferred` chapters (31 of 52) can be built, played and tested, but never locked or released until the episode check changes their tag. The Unity story gate enforces this in release builds. Do not weaken it, remove it, or flip tags yourself.
3. **Licensing.** Only CC0, CC BY and (fonts) SIL OFL assets enter the game, always through `scripts/asset_fetch.py` so the ledger records them. Never download models of the licensed characters from fan or marketplace sites.
4. **No game-over.** Failure is a setback that returns to a checkpoint (`FailForwardManager`). Named allies are freed, never defeated. No gore. These are product rules, not style preferences.
5. **Prove, do not claim.** A step is done only when its command output says so. Report real output, including failures.
6. **Secrets.** Tokens go in environment variables or the CI secret store. Never write them into files, logs or commits.
7. **Never fabricate.** No invented data, no unfinished features presented as finished, no invented episode content, no invented asset licences.

## The pipeline

Work in phases. Each phase has a gate. Record progress with `python3 scripts/progress.py` inside the game project so a later session
can resume exactly where you stopped (`progress.py next` tells you what is next).

### Phase 1: scaffold and compile (gate: zero compiler errors, EditMode tests green)

```
python3 scripts/scaffold_project.py --project <GAME_DIR> --with-docs
python3 scripts/unity_cli.py compile --project <GAME_DIR>
python3 scripts/unity_cli.py test --project <GAME_DIR> --mode editmode
```

The scaffolder creates the Unity project, installs the packages first (the game code cannot compile until the Input System, AI Navigation and
the other packages exist, so only the small `Bootstrap` installer is copied at that point), then copies the game code. If it reports that
no editor was found, install Unity and run `python3 scripts/unity_cli.py install-packages --project <GAME_DIR>` before compiling.

The templates were type-checked against API stubs, not against the real Unity API. If `compile` reports errors, fix them in the
project's `Assets/Game` using the real error text, re-run, and repeat until clean. Then fix the same issue in the skill's
`templates/` copy and tell the human which templates needed correction. See `references/02-unity-automation.md`.

### Phase 2: the playable greybox of all 52 chapters (gate: the full game is playable end to end)

```
python3 scripts/unity_cli.py generate-scenes --project <GAME_DIR>
python3 scripts/unity_cli.py validate --project <GAME_DIR> --require-scenes
python3 scripts/unity_cli.py test --project <GAME_DIR> --mode playmode
```

`SceneGenerator` builds a Bootstrap scene and one scene per chapter (path of objective triggers, checkpoints, fragment pickups,
enemies, timers, stealth and corruption hazards from each chapter's failure rules, chapter exit). The Bootstrap scene runs chapters 1
to 52 in order. Open `Bootstrap` and press Play to check it. This is the proof that the whole game structure works. It is greybox:
everything after this phase is replacing greybox with real content, one chapter at a time, without breaking the loop.

### Phase 3: pre-production gate and vertical slice (gate G1 then G2 of the project document)

1. **Prototype gate (G1):** movement, camera, sword combat and the Shadow must feel good for ten minutes. Playtest with a human; tune values in the components, not in code constants.
2. **Episode check:** run `python3 scripts/story_report.py --out Docs/episode-check.md`. Ask the human to watch the listed episodes (Season 2 first, because it has the least verified content) or to paste synopses. Follow `references/08-episode-check.md`.
3. **Vertical slice:** chapters 1, 5 and 7 to near-final quality (see `references/04-chapter-production.md`): real environment kits, character stand-ins with animation, audio, VFX, cutscenes, localisation keys. Then run the slice playtest protocol (`references/project/09-quality-assurance-and-testing.md`). The slice decides go or no-go (G2): stop and report.

### Phase 4 and 5: Part One, then Part Two (gates G3 and G4)

Per chapter, follow the nine stage gates in `references/04-chapter-production.md`. Work in episode drops (chapters 1 to 9, 10 to 18, 19 to 26, then Season 2 in the same rhythm).
After every chapter: `unity_cli.py compile`, `unity_cli.py test` (both modes), `unity_cli.py validate`, `progress.py set <n> <stage>`.
A chapter reaches `lock` only if it is `Verified`; `progress.py` refuses otherwise.

### Phase 6: release (gate: story gate passes, checklist complete)

```
python3 scripts/license_ledger.py verify --ledger <GAME_DIR>/Assets/ThirdParty/ledger.json --base <GAME_DIR>
python3 scripts/license_ledger.py credits --ledger <GAME_DIR>/Assets/ThirdParty/ledger.json --out <GAME_DIR>/CREDITS.md
python3 scripts/unity_cli.py build --project <GAME_DIR> --target win64 --release
```

A release build fails while any included chapter is not `Verified`. That is correct behaviour. Follow `references/05-qa-ci-release.md` for the checklist, Steam setup and rollback.

## Using the connectors

- **Unity MCP** (editor control: create scenes, objects, components, run tests, read the console). Connection and tool use: `references/01-setup-and-connectors.md`. Use it for scene and prefab work. Use `unity_cli.py` for anything that must be repeatable or that CI also runs.
- **Blender MCP** (modelling, import, Poly Haven and Sketchfab inside Blender). Use it to adapt downloaded assets, retarget or convert files. Final licensed-character models are never fetched, they are authored.
- **Asset scripts** (`scripts/asset_fetch.py`): the default way to download. The catalogue of what the game needs is `data/asset-needs.json`.

If a connector is not installed or not running, say so and fall back to batch mode (`unity_cli.py`). Do not fake connector output.

## When to stop and ask the human

Stop and ask, in one short message, at these points and no others unless blocked: Unity or its licence is missing; the project location is unknown; an episode check is needed; a licence is unclear for an asset you want; a design decision changes a fact in the bible; the slice is ready for the go or no-go review; a release or store action needs their account.
When blocked by something outside your control, say exactly what you need and what you did already.

## Reporting

After each phase or chapter, report: what you ran, the real result, what changed (files), what is verified and what is still `Inferred`, and the next step from `progress.py next`. Keep it short and factual.

## File map

```
SKILL.md                      this file
references/00-agent-playbook.md      rules, decisions, definitions of done
references/01-setup-and-connectors.md  Unity and Blender MCP, tokens, Claude Code and Antigravity setup
references/02-unity-automation.md    batch mode, MCP use, the compile-fix loop
references/03-asset-pipeline.md      sources, licences, import, conversion, budgets
references/04-chapter-production.md  stage gates and recipes per chapter type
references/05-qa-ci-release.md       tests, CI, story gate, Steam, rollback
references/06-troubleshooting.md     agent-side problems and fixes
references/07-template-code-map.md   every C# file and where to extend it
references/08-episode-check.md       how to verify Inferred chapters
references/bible/                    the full production bible
references/project/                  the full engineering and delivery document
data/chapters.json                   the 52 chapters, machine-readable
data/asset-needs.json                what assets the game needs and where to get them
data/allowed-licenses.json           the licence policy
scripts/                             tooling (see each script's --help)
templates/unity/                     the Unity C# foundation, copied into the game project
templates/ci, templates/project      CI workflow, .gitignore, .gitattributes
mcp/                                 ready-to-merge MCP configuration files
tests/                               tests for the scripts, and the C# type-check
```
Files in this package (145)
  • SKILL.md 13 KB
  • data/allowed-licenses.json 1 KB
  • data/asset-needs.json 22 KB
  • data/chapters.json 125 KB
  • mcp/antigravity.mcp_config.json 1 KB
  • mcp/claude-code.mcp.json 1 KB
  • references/00-agent-playbook.md 6 KB
  • references/01-setup-and-connectors.md 4 KB
  • references/02-unity-automation.md 5 KB
  • references/03-asset-pipeline.md 5 KB
  • references/04-chapter-production.md 7 KB
  • references/05-qa-ci-release.md 5 KB
  • references/06-troubleshooting.md 5 KB
  • references/07-template-code-map.md 6 KB
  • references/08-episode-check.md 4 KB
  • references/bible/00-index.md 2 KB
  • references/bible/01-document-control-and-source-policy.md 2 KB
  • references/bible/02-vision-and-pillars.md 1 KB
  • references/bible/03-story-bible.md 5 KB
  • references/bible/04-characters.md 4 KB
  • references/bible/05-world-and-locations.md 2 KB
  • references/bible/06-core-gameplay-systems-all-g.md 4 KB
  • references/bible/07-failure-rules.md 2 KB
  • references/bible/08-difficulty-accessibility-and-audience-safety.md 1 KB
  • references/bible/09-chapter-template-and-master-overview.md 5 KB
  • references/bible/10-season-1-chapters-part-one.md 26 KB
  • references/bible/11-season-2-chapters-part-two.md 10 KB
  • references/bible/12-boss-and-set-piece-list.md 2 KB
  • references/bible/13-progression-and-fragment-tracker.md 1 KB
  • references/bible/14-art-audio-and-interface-direction.md 1 KB
  • references/bible/15-production-plan.md 2 KB
  • references/bible/16-glossary-of-names-and-variants.md 1 KB
  • references/bible/17-open-items-and-episode-check-list.md 1 KB
  • references/bible/18-sources.md 1 KB
  • references/project/00-index.md 2 KB
  • references/project/01-summary-of-decisions.md 2 KB
  • references/project/02-scope-goals-and-constraints.md 2 KB
  • references/project/03-feasibility.md 3 KB
  • references/project/04-tech-stack.md 4 KB
  • references/project/05-system-architecture.md 5 KB
  • references/project/06-chapter-design-pipeline.md 3 KB
  • references/project/07-coding-guide-with-reference-implementations.md 4 KB
  • references/project/08-content-pipeline-and-tooling.md 3 KB
  • references/project/09-quality-assurance-and-testing.md 3 KB
  • references/project/10-performance-and-platform-targets.md 2 KB
  • references/project/11-troubleshooting-guide.md 5 KB
  • references/project/12-deployment-and-release.md 5 KB
  • references/project/13-project-plan-team-and-milestones.md 4 KB
  • references/project/14-risk-register.md 2 KB
  • references/project/15-legal-ethics-privacy-and-child-safety.md 1 KB
  • references/project/16-product-and-business-options.md 1 KB
  • references/project/17-metrics-and-success-measures.md 1 KB
  • references/project/18-appendices.md 3 KB
  • scripts/_common.py 3 KB
  • scripts/asset_fetch.py 13 KB
  • scripts/blender_gltf_to_fbx.py 1 KB
  • scripts/check_env.py 3 KB
  • scripts/ledger.py 4 KB
  • scripts/license_ledger.py 1 KB
  • scripts/progress.py 4 KB
  • scripts/scaffold_project.py 7 KB
  • scripts/story_report.py 3 KB
  • scripts/unity_cli.py 9 KB
  • scripts/validate_chapters.py 6 KB
  • templates/ci/unity-ci.yml 3 KB
  • templates/project/.gitattributes 1 KB
  • templates/project/.gitignore 1 KB
  • templates/unity/Assets/Game/Bootstrap/Farhat.Bootstrap.Editor.asmdef 1 KB
  • templates/unity/Assets/Game/Bootstrap/PackageInstaller.cs 2 KB
  • templates/unity/Assets/Game/Content/Data/chapters.json 125 KB
  • templates/unity/Assets/Game/Editor/BuildScript.cs 3 KB
  • templates/unity/Assets/Game/Editor/ChapterBoardWindow.cs 2 KB
  • templates/unity/Assets/Game/Editor/ChapterCatalogImporter.cs 5 KB
  • templates/unity/Assets/Game/Editor/ContentValidator.cs 5 KB
  • templates/unity/Assets/Game/Editor/Farhat.Editor.asmdef 1 KB
  • templates/unity/Assets/Game/Editor/PrefabBuilders.cs 9 KB
  • templates/unity/Assets/Game/Editor/ProjectSetup.cs 2 KB
  • templates/unity/Assets/Game/Editor/SceneGenerator.cs 22 KB
  • templates/unity/Assets/Game/Editor/StoryGate.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Farhat.Runtime.asmdef 1 KB
  • templates/unity/Assets/Game/Runtime/Core/EventBus.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Core/Events.cs 3 KB
  • templates/unity/Assets/Game/Runtime/Core/GameObjectPool.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Core/ServiceLocator.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Core/StateMachine.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Data/ChapterCatalog.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Data/ChapterDefinition.cs 3 KB
  • templates/unity/Assets/Game/Runtime/Data/ChapterJson.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Data/DialogueSequence.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Data/EnemyDefinition.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Data/Enums.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Data/PotionRecipe.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Save/SaveData.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Save/SaveMigrator.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Save/SaveSystem.cs 3 KB
  • templates/unity/Assets/Game/Runtime/Save/SettingsProfile.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Story/ChapterRunner.cs 7 KB
  • templates/unity/Assets/Game/Runtime/Story/ChapterScoring.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Story/CheckpointStore.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Story/DialogueRunner.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Story/FailForwardManager.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Story/GameBootstrap.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Story/HintService.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Story/LevelAnchors.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Story/LevelTriggers.cs 10 KB
  • templates/unity/Assets/Game/Runtime/Story/ObjectiveTracker.cs 3 KB
  • templates/unity/Assets/Game/Runtime/Story/ScreenFader.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Story/UnlockManager.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Systems/AlchemyInventory.cs 6 KB
  • templates/unity/Assets/Game/Runtime/Systems/AwarenessMeter.cs 3 KB
  • templates/unity/Assets/Game/Runtime/Systems/AwarenessSensor.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/CombatController.cs 6 KB
  • templates/unity/Assets/Game/Runtime/Systems/CompanionFollower.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Systems/DecodePuzzle.cs 2 KB
  • templates/unity/Assets/Game/Runtime/Systems/EnemyBrain.cs 6 KB
  • templates/unity/Assets/Game/Runtime/Systems/HazardZone.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Systems/HealthComponent.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Systems/Interfaces.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/KillVolume.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/LightMeter.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Systems/PlayerController.cs 6 KB
  • templates/unity/Assets/Game/Runtime/Systems/PlayerInputActions.cs 4 KB
  • templates/unity/Assets/Game/Runtime/Systems/ProtectedAlly.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/RuntimeNavMeshBaker.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/SafePointRecorder.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/ShadowController.cs 8 KB
  • templates/unity/Assets/Game/Runtime/Systems/ShadowGap.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/ShadowRevealable.cs 1 KB
  • templates/unity/Assets/Game/Runtime/Systems/ThirdPersonCamera.cs 3 KB
  • templates/unity/Assets/Game/Runtime/UI/ChapterTitleCard.cs 2 KB
  • templates/unity/Assets/Game/Runtime/UI/HudController.cs 2 KB
  • templates/unity/Assets/Game/Runtime/UI/QuestLogView.cs 2 KB
  • templates/unity/Assets/Game/Runtime/UI/SubtitleView.cs 1 KB
  • templates/unity/Assets/Game/Tests/EditMode/ChapterDataTests.cs 7 KB
  • templates/unity/Assets/Game/Tests/EditMode/CoreTests.cs 10 KB
  • templates/unity/Assets/Game/Tests/EditMode/Farhat.Tests.EditMode.asmdef 1 KB
  • templates/unity/Assets/Game/Tests/PlayMode/ChapterSmokeTests.cs 8 KB
  • templates/unity/Assets/Game/Tests/PlayMode/Farhat.Tests.PlayMode.asmdef 1 KB
  • templates/unity/Assets/Game/Tests/PlayMode/SystemTests.cs 6 KB
  • tests/test_assets.py 12 KB
  • tests/test_chapters.py 4 KB
  • tests/test_skill_integrity.py 5 KB
  • tests/test_tooling.py 8 KB
  • tests/csharp-compile-check/UnityStubs.cs 20 KB
  • tests/csharp-compile-check/check.sh 1 KB

Versions

The database has no other skills named farhat-unity-builder.

Database snapshot: 13.11.2026 · package version f1fa74c1d56e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100unity-mobile-game-development
    Use when building, restructuring, profiling, testing, or packaging a Unity mobile game in C# for Android or iOS; covers project architecture, scenes, prefabs, data, input, assets, saves, builds, and Unity-specific release evidence.
  • 100game-prototype-builder
    Unity / Godot Prototype Builder: When project files and execution tools exist, verify the installed engine and run the engine build. Use when the user asks for unity / godot prototype builder work, or mentions game, prototype, builder.
  • 90scenoco-game
    Make or change a browser game with SceNoCo — three.js scenes in TSX (no React) and Unity's behaviours, from the @scenoco-three npm packages. Use when asked to build a 2D or 3D web game with SceNoCo, three.js and Unity-style behaviours, to add a game to a React app, or to test or…
  • 100unity-dev
    Use when implementing a Unity C# feature or fix, or when the user requests Unity architecture, implementation, review, or tests.
  • 90unity-project-audit
    Use when the task is to inspect Unity project settings, packages, scenes, and build targets.
  • 91build-world
    Builds polished, fully playable 3D game prototypes in three.js, Roblox, Unity, or Unreal Engine, with high-quality (.glb/.fbx) meshes from the Thrixel API, and (for three.js and Unity) publishes finished games to a public thrixel.world link that anyone can play in a browser. Use…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.