Game Vibe Code

Runs an AI-agent build loop from idea to a playable, verified, shippable game: one-page spec, playable in the first hour, one feature per iteration with a pass/fail check, Playwright screenshots, commits and a progress.md handoff. Use for "vibe code a game", "build a game with Claude", "make a browser game fast". Not for throwaway mechanic tests (use game-prototype).

57 stars 6 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add AlterLab-IEU/AlterLab_GameForge

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-vibe-code
Manual install
git clone --depth 1 https://github.com/AlterLab-IEU/AlterLab_GameForge.git /tmp/AlterLab_GameForge
mkdir -p ~/.claude/skills
cp -r /tmp/AlterLab_GameForge/skills/workflows/game-vibe-code ~/.claude/skills/game-vibe-code

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# AlterLab GameForge -- Vibe Code Loop

You are **Juno Reyes**, a game developer who builds and ships small games with coding agents, and
who writes specs and handoff notes like a technical writer. You like the speed. You distrust "all
tests pass" without output, screenshots nobody opened, and any file nobody can explain. Your loop
is short: decide what done looks like, let the agent build it, prove it by playing, commit, write
down what changed.

Andrej Karpathy coined "vibe coding" on 2 Feb 2025: give in to the vibes and "forget that the code
even exists." That is fine for a weekend toy. Once you want to ship, patch, or hand the work to the
next session, forgetting the code becomes **vibe debt**: code without structural rationale that no
session can change safely. This skill keeps the speed and adds receipts. Every iteration ends in a
check that comes back pass or fail, a screenshot someone actually looked at, and a commit.

**Continuity lives in files, not memory.** Read these first and update them last:
`design/vibe-spec.md`, `CLAUDE.md`, `progress.md`, `docs/iteration-log.md`, and
`production/session-state/active.md`. Background and sources:
`${CLAUDE_PLUGIN_ROOT}/docs/vibe-coding.md`.

## When to Use Me

- Building a small, complete game with Claude Code, from idea to playable to shipped.
- An AI-friendly jam (Vibe Jam-style rules, or prepping coding agents for a jam).
- Resuming an agent-built game from `progress.md`.
Read the full skill on GitHub

Details

Skill name
game-vibe-code
Path
skills/workflows/game-vibe-code/SKILL.md
License
MIT
Repo updated
6 November 2026

FAQ

What does the Game Vibe Code skill do?

Runs an AI-agent build loop from idea to a playable, verified, shippable game: one-page spec, playable in the first hour, one feature per iteration with a pass/fail check, Playwright screenshots, commits and a progress.md handoff. Use for "vibe code a game", "build a game with Claude", "make a browser game fast". Not for throwaway mechanic tests (use game-prototype).

How do I install the Game Vibe Code skill?

Claude Code plugin: /plugin marketplace add AlterLab-IEU/AlterLab_GameForge. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Game Vibe Code popular?

It lives in AlterLab-IEU/AlterLab_GameForge, which has 57 GitHub stars and 6 forks, and is included in 1 curated skill list.

Related skills

Game Accessibility Specialist

57

AlterLab-IEU/AlterLab_GameForge

Accessibility Specialist (Kael Oduya). Designs motor, visual, auditory and cognitive accommodations, runs accessibility audits, scopes the European Accessibility Act, CVAA and Game Accessibility Guidelines, and maps fixes to Godot, Unity, Unreal or web. Use for "accessibility audit", "EAA", "colorblind", "subtitles", "remapping". Not for general UX flows (use game-ux-designer).

Frontend & DesignIn 1 list

Game AI Assets

57

AlterLab-IEU/AlterLab_GameForge

Runs an AI-assisted asset pipeline for models, sprites, textures, audio and voice: generate vs make vs buy, license-first tool choice, style lock, engine post-processing, and a per-asset provenance log for Steam, itch.io and EU AI Act disclosures. Use for "generate a sprite with AI", "ElevenLabs", "can I ship this AI asset". Not for defining art style (use game-art-director).

AI, LLMs & AgentsIn 1 list

Game Analytics Setup

57

AlterLab-IEU/AlterLab_GameForge

Sets up privacy-first game analytics: question-driven event taxonomies, consent-gated telemetry (GDPR, COPPA, ATT), engine and web SDK choice, KPI definitions, dashboards, A/B tests, and AI feedback summaries validated against real data. Use for "analytics", "telemetry", "KPIs", "retention", "funnel", "A/B test". Not for balance tuning (use game-balance-check).

Data & AnalyticsIn 1 list

Pannelai Web Search

49

rusmanadodi2598/pannelAI

Web search through pannelAI. Covers POST /api/v1/search, how the provider is named, the query and max_results fields, and the normalized results envelope with its cost and timing. Use when a client needs live web results from the gateway.

Software Development

Game Godot Specialist

57

AlterLab-IEU/AlterLab_GameForge

Writes and reviews Godot 4 code (4.7 stable, 4.8 beta) in GDScript and C#: scenes and nodes, signals, Resources, autoloads, Jolt physics, shaders, profiling, export, GUT/gdUnit4 tests and headless CLI checks. Use when the project has project.godot, .gd or .tscn files, or the user mentions Godot or GDScript. Not for engine-agnostic architecture (use game-technical-director).

Software DevelopmentIn 1 list

App Store Submission Auditor

33

itsncki-design/app-store-submission-auditor

Scans an iOS app project for App Store rejection risks. Reads source code directly — no back-and-forth. Auto-detects vibe coder vs developer and adapts language. Detects mid-build apps and asks before switching modes. Outputs a risk register, detailed findings with dynamic copy-paste fixes, reviewer experience checklist, draft App Store Connect reviewer notes, and a post-scan manual checklist. TRIGGER THIS SKILL for any of these — even if not explicitly asked: "audit my app" / "is my app ready" / "about to submit" / "submitting soon" / "about to launch" / "ready to ship" / "App Store review" /

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.