Arcade Skill / Play / Support

A Retro Break Game For Claude Code Wait Time

Search intent: Users who want a harmless local arcade break instead of doom-scrolling during agent waits.

Real datapoint: The hosted play route is https://arcade.fxpeek.com/play/ and the installed skill uses https://arcade.fxpeek.com/manifest.json for updates.

Keyword focus: Claude Code break game

This page is written for developer search intent.

The waiting-room problem

Modern coding agents changed the rhythm of programming. A developer asks Codex, Claude Code, or another assistant to install dependencies, run tests, inspect diffs, or regenerate code. For the next few minutes the human is present but not fully occupied. Opening a social feed breaks attention. Starting a large game is too heavy. Arcade Skill targets that narrow gap: a quick, local-first, retro-feeling arcade loop that ends before the agent has forgotten why it was working.

The first game, Down 100 Floors, uses a tiny falling-platform challenge: move left and right, land on platforms, avoid spikes, and try to reach a deeper floor than last time. The character is intentionally simple and readable, closer to a nostalgic terminal toy than a modern gacha product. That is the point. The game should feel like something a developer can launch between test runs without guilt.

Why it is different from a generic browser-game portal

Arcade Skill is distributed as an agent skill and as a hosted web page. The installed skill opens a verified bundle through a thin Python loader. The loader fetches a manifest, checks sha256, swaps the local cache atomically, and falls back to the last good version when a network or hash check fails. This means new games, copy changes, support links, emergency notices, and kill switches can ship without asking every installed user to download a new package.

The hosted version exists for sharing, search, screenshots, ranking, and future web-only ads. The local skill version deliberately keeps AdSense disabled because localhost sessions are not a real ad surface. That separation protects trust with developers and keeps the product honest: the installed skill is a tiny break and acquisition loop, while the public website is where discoverability and monetization experiments belong.

Fair-play rule

The ranking model is simple. Deeper floor wins. Time breaks ties. Stripe support, sponsorship, or future supporter perks must never buy health, revives, or leaderboard advantage. That rule matters because the social loop depends on score credibility. A nostalgic arcade challenge loses its charm the moment payment changes the run.

How to use it

Use the hosted route when you want to share a score or test the game immediately: arcade.fxpeek.com/play. Use the skill package when you want your coding agent to open a quick local arcade break while it works. The ideal invocation is plain language: tell your agent that you are waiting on tests and want a quick game.

Frequently asked questions

Is this for serious gaming?

No. It is a short-break arcade toy for developer wait time. The win condition is not hours of retention; it is a clean two-minute loop that does not derail the work session.

Does it collect telemetry?

Telemetry is used to understand game balance and growth loops: death floor, session length, share clicks, and support clicks. The roadmap keeps publishing and outreach human-reviewed.

Generated

2026-07-11. This draft is safe to review, edit, and publish through the normal repo flow.