SlopScore
00 crowd

chessgame

A very basic Chess game, as a Swift executable package, for macOS, built with Cursor.AI.
Open repo on GitHubgithub.com/drewster99/chessgame
Swift · ★ 1 · 0 forks · MIT · paperwork by the Cap'mmostly ai (inferred)light human (inferred)works-on-my-machine (inferred)other
listed 2 hours ago by drewster99 · last checked 51 minutes ago
The owner didn't write this. This repo never submitted itself. The Cap'm found it on a truffle trawl and wrote its paperwork from what GitHub already shows. Picked by hand by the Cap'm on 2026-09-13: A very basic Chess game, as a Swift executable package, for macOS, built with Cursor.AI.; its own README says "A very basic Chess game, as a Swift executable package, for macOS, built with Cursor". 1 stars; MIT license. The owner did not submit this. Votes count; awards don't until the owner claims it.

I'm not calling your project slop! Geeze, it's a joke... Do you own this repo?

Log in with GitHub as drewster99. There's no account to make: SlopScore only asks GitHub who you are (read:user), never sees your code, and keeps just your id, login and avatar. Then you can:

  • Keep it, on your terms. Commit your own slopscore.md (spec) and press Refresh. Your paperwork replaces the Cap'm's, and you can submit it for Slop of the Day.
  • Take it down. One click on Remove. It stays gone; the trawl never brings it back.

Log in with GitHub

Can't log in as the owner? Request a takedown. No login needed, and a trawled listing comes down right away.

GitHub says
A very basic Chess game, as a Swift executable package, for macOS, built with Cursor.AI.
created
2025-01-01 · pushed 1 week ago · 8 commits · 1 contributor
languages
Swift 97%Shell 3%
paperwork
licensereadme 42% health
dependencies
no dependency graph (no manifest, or disabled) · OSV.dev, checked 2 hours ago

Disclosures, inferred by the Cap'm

slopbucket
vibe-coded
category
other
ai_generated
mostly
human_touch
light
status
works-on-my-machine
language (detected)
shellswift
license (detected)
mit

The Cap'm's log

The Cap'm wrote this paperwork, not the owner. This repo never submitted itself to SlopScore. The Cap'm picked it by hand: A very basic Chess game, as a Swift executable package, for macOS, built with Cursor.AI.; its own README says "A very basic Chess game, as a Swift executable package, for macOS, built with Cursor". It carries the MIT license. The disclosures above are his best guess from what GitHub shows.

Is this yours? Commit a real slopscore.md and press Refresh to replace this, or remove the listing in one click. There's no account to make: you log in with GitHub.

README — the repo's own words, folded up so the grading fits on one screen

ChessGame

A very Chess game for macOS, in the form of an executable Swift package, built with Cursor.AI.

Screenshot

Screenshot 2025-01-01 at 8 35 51 PM

How It Was Made

This, admittedly very basic, Chess game was built almost entirely using Cursor.AI. I didn't write a single line of code (so far!), so everything here was generated as a result of various AI prompts and interactions, all with the "Cursor" macOS app. The only exception are the images of the pieces themselves. I pulled those from somewhere (maybe wikimedia?) and renamed them to names the AI had requested. Cursor also made the asset catalog entries, though in looking at it now, it seems odd that the images themselves are just in the root and not down in the Resources folder

How to Build and Run

  1. Clone this repo
  2. Open the Package.json in Xcode
  3. Make the destination your Mac, and then do Build and Run (Command-R)

Note: We should be able to run this from the build script or using "swift build", but for some reason when I do that, the Assets.xcassets doesn't get processed into a .car file, and SwiftUI can't find any of the images. What's up with that? Anybody know why?

Anyway, I'm placing this initial version here as a point-in-time example of what current AI coding tools can do.

Limitations and Issues

  1. Well, White goes first of course, but the computer won't make the first move, so right now you need to move the white piece first, and then move a black piece. After that, white will take its turn automatically.

  2. To move, you need to click on the piece you want to move, then click on the new square. However, there's no way to reset the selected piece, so once you've clicked one, you HAVE to move that piece.

Read the rest on GitHub

Scan report · 2026-09-13
  • Prohibited terms or links
  • Repository eligibility
  • slopscore.md paperwork
  • Content policy
  • Risk review

0 comments

log in to comment.

report this listinglog in to report