ShadowOfTheColossus-PC
Native Windows port of Shadow of the Colossus (PS4, CUSA08809) - bring your own game dump. Port nativo para PC.
Every game and lab in the Game-Template-and-Library repository, built from its code: play any of them in the browser.
GamesJavaScript · TypeScriptGitHub @william-are-buzbeeOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗Every game, experiment and shared system in one place: games in games/, one-shots and tech demos in labs/,
systems shared by two or more of them in packages/. CATALOG.md lists everything that exists;
the site plays everything: https://william-are-buzbee.github.io/Game-Template-and-Library/
The code is written by Claude and reviewed and merged by the person; the rules for that are in CLAUDE.md, the repository settings in docs/standard.md, and what was decided and why in docs/decisions.md.
Say it in a prompt: "a new game: …" or "a lab to try …". Claude scaffolds it (npm run new), builds it, and opens a
pull request; the pull request's preview link plays it before you merge.
Needs Node.js 22.18 or later.
npm install once, and whenever a package.json changes
npm run dev -w games/<name> play a game while working on it (reloads on save); labs/<name> likewise
npm run check types, the catalog, and the tests of what you changed (check:all: every test)
npm run build build everything
npm run new -- game <name> "<one line>" start a game (or: lab)