Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

ScreenPlink Built With Claude Code Turns a Monitor Into a Laser Target

AI summary

Developer vkorost reports building the open-source ScreenPlink laser dry-fire game with Claude Code in about two weeks, with the coding agent writing essentially all the code. The Windows game uses a webcam to identify laser-hit pixels, display bullet holes and knock down targets, while an in-process MCP server exposed measurements and debug data to Claude Code. The developer also says the project requires a matte monitor, a 60 fps webcam and a red laser trainer, and that glossy screens and TVs are unsupported.

In-depth insight

ScreenPlink provides a detailed, source-backed case study in using Claude Code for computer-vision software, physical-world debugging and mutation testing, although its performance figures and development claims come from the developer.

I built ScreenPlink with Claude Code over about two weeks. It is a laser dry-fire shooting game where your monitor is the target. You shoot the screen with a laser trainer pistol, or with a laser cartridge in your own gun. A webcam sitting beside the monitor watches the screen rather than you, the app works out which pixel you hit, punches a bullet hole there, and the target falls. Nine drills, fifteen figures with scoring rings, a 17-round magazine, and two players on one screen. You can also take both halves yourself with a pistol in each hand: two lasers landing in the same camera frame are detected as two separate shots. The 90-second trailer shows what the game looks like. The camera does not need to be in front of the screen or square to it. Off-axis at an angle is normal and supported: the app photographs its own markers on the monitor to learn the mapping, so calibration costs no ammunition. How Claude Code was used to build it Claude Code wrote essentially all of the code. I designed the game, directed Claude, shot at the monitor, and ruled on what was acceptable, but I did not write any code by hand. The hard part was never the game logic. It was getting an agent to develop and debug a program that measures the physical world, when the agent cannot see the monitor or pull the trigger. The honest headline number is not a test result: an independent microphone channel counts trigger pulls separately from the camera, and 84 to 89% of heard trigger pulls become a detected shot. All twenty lessons learned are described in details in the repo. Free to try, two ways to set up Open source (Apache-2.0), source plus a Windows release: https://github.com/vkorost/screenplink What you need: Windows, a matte (anti-glare) monitor, a webcam that does 60 fps, and a red laser trainer. Glossy screens and TVs do not work. submitted by /u/vkorost [link] [comments]

#ScreenPlink#Claude Code#Anthropic#Model Context Protocol

Original · 2 min readRead the original
Group chat

No comments yet. Start the conversation.