claudeers.
// Claude Skills

deepseek-harness-game-studios

DeepSeek Harness port of Claude Code Game Studios (CCGS v1.1.2, MIT) — one-package install: hook bridge (9 events), studio status line, self-installing frame…

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up deepseek-harness-game-studios (git-clone project) into my current project.
Found on https://claudeers.com/deepseek-harness-game-studios
Repo: https://github.com/HYClub/deepseek-harness-game-studios
Homepage/docs: —
Detected install method: git-clone → git clone https://github.com/HYClub/deepseek-harness-game-studios
Category: skills. Platforms: cli, api, desktop, web, mobile.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or clone
git clone https://github.com/HYClub/deepseek-harness-game-studios

// compatibility

Platformscli, api, desktop, web, mobile
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageJavaScript

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

DeepSeek Harness Game Studios

Install · Implementation status · Project structure · Testing your customizations · Verification · License

Turn a single DeepSeek Harness session into a full game development studio. 49 agents. 79 skills. One coordinated AI team.

This is a port of Claude Code Game Studios (CCGS) to DeepSeek Harness (DSH) — not a rewrite from scratch: the skills, agents, rules and docs come from upstream (MIT); this repository provides the DSH-native runtime (Node hooks, skill generation, machine-level install, plugin bridge).

Provenance

Upstream projectDonchitos/Claude-Code-Game-Studios
Upstream version this port tracksv1.1.2 (commit b21fa0f, 2026-09-29)
Upstream licenseMIT (Copyright © 2026 Donchitos) — reused here
This repositorydeepseek-harness-game-studios (DSGS) v0.2.3
Port strategyDual stack, one source: .claude/ is the content source (upstream text, kept verbatim); .dsh/** is generated by tools/build-dsh.mjs

Upstream targets Claude Code (.claude/, .sh hooks, bash one-liners, @path imports). None of that runs under DSH (no bash tool, piped child processes are denied by the sandbox, @path is not expanded), so instead of editing upstream content we generate a DSH-runnable equivalent and prove no content loss.

The plugin package bundles the framework under payload/ — you never need to look at it while using the plugin.

Install

① Web client

Plugins → Add plugin → paste https://github.com/HYClub/deepseek-harness-game-studios → Install → restart dsh web.

dsh plugin --profile web add https://github.com/HYClub/deepseek-harness-game-studios

② Desktop client

Open the desktop app, then Plugins → Add plugin → paste the same URL → Install → restart the app.

On first load the plugin installs the framework at machine level (~/.dsh/dsgs plus user-level bootstrap skills). After that:

new working directory → new session → type /start

/start checks whether the workspace is initialised; if not it initialises it first, then walks you through onboarding.

Upgrade

Run /update inside an initialised workspace (0.2.1 and later):

/update

It reads the installed version and the newest release, shows the commands it will run, and runs them only after you agree. Restart the client afterwards — the new skills appear in a new session.

Is this workspace initialised? Yes when .dsh/skills/start/SKILL.md or .dsgs-installed.json exists in the project root. If neither is there, open the project in DSH, start a new session and type /start: that initialises it once, and every later session in the same project can use /update.

Coming from 0.2.0 or earlier? /update only exists from 0.2.1 on, so the first update is manual:

dsh plugin --profile web remove deepseek-harness-game-studios
dsh plugin --profile web add https://github.com/HYClub/deepseek-harness-game-studios

Desktop app users do the same through Plugins (see below). Every update after that is one /update.

Desktop app — the app owns its plugin profile, so the command line cannot change it. Open Plugins, uninstall deepseek-harness-game-studios, choose Add plugin, paste https://github.com/HYClub/deepseek-harness-game-studios, install, then restart the app. /update still reports the version and tells you when this is needed.

What the plugin writes to your machine (and how to undo it)

PathWhat
~/.dsh/dsgs/**framework payload (skills, agents, rules, hooks, tools, docs, instruction files)
~/.dsh/skills/dsgs-init/SKILL.md, ~/.dsh/skills/start/SKILL.mduser-level bootstrap skills

It never touches a project directory and never overwrites project files. To undo:

Remove-Item -Recurse -Force "$env:USERPROFILE\.dsh\dsgs"
Remove-Item -Recurse -Force "$env:USERPROFILE\.dsh\skills\dsgs-init","$env:USERPROFILE\.dsh\skills\start"
# then uninstall the plugin and restart dsh web

Implementation status

✅ Implemented (all measured)

ItemStatusNotes
Skills✅all 74 upstream skills ported, each invocable as /name
Agent role cards✅49, as .dsh/agents/<name>.md + delegation conventions
Rules✅13, including an equivalent for upstream's path-scoped rule engine: a PostToolUse hook injects the matching rule text after each write/edit
Hooks✅13 upstream hook scripts → 14 Node implementations (one DSH-only addition), bridged via dsh-hooks-claude-code; all 9 upstream events covered
Hooks actually run✅mount 10/10 · protocol 12/12 · live events 6/9 — measured on a host where the official bridge package is installed; elsewhere the checks report SKIP instead of a false failure
Config resolution✅project.yaml single source; Node ports of resolve_config / __call resolve_setting
Helper scripts✅every upstream .sh has a Node port (.dsh/scripts/*.mjs) that runs inside the sandbox
Content fidelity✅258 files / 42,895 lines: 96.0% verbatim, 3.1% documented rewrites, 0.5% structural, 0.4% fuzzy, 0 unexplained loss
Machine-level install✅the plugin ships the payload (924 files) and installs it on first load; /start then initialises an empty workspace from it
/statusline✅studio status line stage · posture · epic > story · Sprint n/m · engine (+13 unit tests)
Nested delegation✅subagent.maxDepth: 2 — parent → child → grandchild verified (DSH default is 1)
Shared rules reach a project✅the @path imports in CLAUDE.md are written out as "read this file" instructions, because this runtime does not expand them — without that, the standards documents were referenced but never read
Role tool boundaries✅every agent role card states the tools its role should stay within, in this runtime's tool names. Advisory: the runtime cannot enforce a per-agent tool set
One-package install✅one package = hook bridge + status line projection + payload self-install
/today✅three to five lines: the next story, what is blocked, the command to run
/dashboard✅one offline HTML board — overview · gaps · expected paths · roster · charts · commands — with three charts for 7 / 30 / 90 days and all time; the left navigation works without JavaScript, light and dark themes follow the system or a remembered choice, and printing stays readable
/update✅compares the installed plugin with the newest release and runs the two commands only after you confirm
DSGS-only skills✅statusline, dsgs-install, today, dashboard, update (not in upstream)

⚠️ Partly equivalent — works, with a stated limit

ItemWhat worksWhat does not, and why
3 hook eventsmapping implemented and unit-testedNotification, PreCompact, PostCompact have no DSH event source, so they are verified at mount level only (live coverage 6/9)
Per-agent tool allowlistsevery role card states the boundary in its body (工具边界 …:read, glob, grep, …), so a delegating model reads itDSH's subagent accepts no per-agent tool set and there is no agent registry, so the runtime cannot enforce it
Byte-for-byte bash ↔ Node parityevery pair that can run matches byte for byte; the two YAML-dependent pairs are counted and asserted (an unexpected skip fails the run; PARITY_REQUIRE_ALL=1 forbids skipping where python3 exists)python3 in this machine's Git Bash is a Store placeholder, so the bash side of those two pairs cannot read YAML

❌ No equivalent — reason and substitute

ItemWhySubstitute
Docked status bar above the composerDSH's client roster only lists @deepseek-ai/* packages (measured: 60+ entries, ours absent even with a dsh.client declaration)/statusline skill + node .dsh/statusline.mjs; the runtime half (turns/tokens/cache/context %) is already covered by DSH's own status bar
Pre-action reminders on PreToolUsetools/pre-execute only carries allow/deny/cancel/ask; additionalContexts is read from the final tool result; agent.inject() mid-execution has no effectvalidate-commit / validate-push are also registered on PostToolUse (reminder arrives after the action); set the plugin row advisory: deny to block before the action
!cmd`` pre-execution linesDSH has no pre-executionrewritten as a "prerequisite command" block the model runs itself

Project Structure

.claude/                     # Upstream content source (MIT, kept verbatim)
  settings.json              # Hooks, permissions, safety rules
  agents/                    # 49 agent definitions
  skills/                    # 74 skills (one directory per skill)
  hooks/                     # 14 scripts — 13 event hooks + yaml-helper.sh
  rules/                     # 13 path-scoped coding standards
  statusline.sh              # Upstream status line (kept as reference)
  docs/                      # workflow catalog, 39 templates, guidance
.dsh/                        # Generated by tools/build-dsh.mjs — do not edit by hand
  agents/  skills/  rules/  hooks/  scripts/  docs/
tools/                       # Generator, verifiers, Node ports, plugin, installers
dsh-src/                     # Hand-written DSH-only overlay (merged into .dsh/)
DSGS Skill Testing Framework/  # QA for the skills and agents themselves
design/ src/ assets/ tests/ prototypes/ production/   # Your project

Testing your own customizations

DSGS is a template you are meant to edit. DSGS Skill Testing Framework/ is how you check that an edited or newly written skill still holds up — a catalog of all skills and agents, per-category quality rubrics, behavioral specs, and templates for writing specs of your own.

/skill-test static [name]     # structural linter
/skill-test category [name]   # category-specific quality rubric
/skill-test spec [name]       # behavioral spec assertions
/skill-test audit             # coverage report across skills and agents
/skill-improve [name]         # test-fix-retest loop; keeps or reverts on score change

It tests the framework, never your game — game tests live in tests/.

Verification

pwsh -File tools/verify-port.ps1        # 7 steps: generate → structure → refs → fidelity → hooks → mount → suites
node tools/check-dsh.mjs                # skills=79 agents=49 rules=13 hooks=14 errors=0 warnings=0
node tools/verify-fidelity.mjs          # unexplained 0 / no content loss (258 files, 42,895 lines)
node tools/verify-hooks-mount.mjs       # 10/10 mount cases
node tools/verify-hooks-bridge.mjs      # 12/12
node tools/verify-hooks-events.mjs      # 6/9 live + 3 mount-only

Supporting this project (and upstream)

DSGS is a port; the original work — 74 skills, 49 agents, 13 rules and all the documentation — was written by the upstream author, and their own support links live in the upstream repository. If this project saves you time, please support them first. Issues and contributions about the DSH port itself belong in this repository.

License

MIT License — see LICENSE. Upstream copyright © 2026 Donchitos; the port layer (generator, Node hooks, plugin, installers, DSGS-only skills) is released under the same license.

// faq

What is deepseek-harness-game-studios?

DeepSeek Harness port of Claude Code Game Studios (CCGS v1.1.2, MIT) — one-package install: hook bridge (9 events), studio status line, self-installing framework payload (76 skills, 49 agents, 13 rules).. It is open-source on GitHub.

Is deepseek-harness-game-studios free to use?

deepseek-harness-game-studios is open-source under the MIT license, so it is free to use.

What category does deepseek-harness-game-studios belong to?

deepseek-harness-game-studios is listed under skills in the Claudeers registry of Claude-compatible tools.

6 views
★ 16 stars
unclaimed
updated 11 days ago

// embed badge

deepseek-harness-game-studios on Claudeers
[![Claudeers](https://claudeers.com/api/badge/deepseek-harness-game-studios.svg)](https://claudeers.com/deepseek-harness-game-studios)

// retro hit counter

deepseek-harness-game-studios hit counter
[![Hits](https://claudeers.com/api/counter/deepseek-harness-game-studios.svg)](https://claudeers.com/deepseek-harness-game-studios)

// reviews

// guestbook

0/500

// related in Claude Skills

🔓

An agentic skills framework & software development methodology that works.

// skillsobra/⟨Shell⟩★ 314,126◷ MIT[ claude ]
🔓

Public repository for Agent Skills

// skillsanthropics/⟨Python⟩★ 188,182[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// skillsGraphify-Labs/⟨Python⟩★ 149,064◷ MIT[ claude ]
🔓

💫 Toolkit to help you get started with Spec-Driven Development

// skillsgithub/⟨Python⟩★ 148,200◷ MIT[ claude ]
→ see how deepseek-harness-game-studios connects across the ecosystem