Welcome to Stop-Slop Studio. I’m Shane. Maybe you’ve been working with AI for a while and you’re tired of getting the same phrases, predictable characters, and prose that sounds suspiciously like everyone else’s. Maybe you have an idea you’ve wanted to make for years, and you’re figuring out where to start. You’re welcome here. We teach you how to get more out of AI while keeping your own judgment and voice in the work. Use it a little or use it a lot. You decide what belongs in your process. Watch the welcome video above, then have a look around: - The Classroom: Start with The First Pass. Bring a page and try the method on something you actually wrote. - The Studio: Explore our writing tools and public benchmark at stopslopstudio.com/studio. You can inspect the work and results for yourself. - Author Cockpit: Our connected creative workspace brings your projects and tools together. Full Cockpit access is part of our paid offering; you don’t need to upgrade to join the conversation and get started here. Writing is our foundation. We’re also exploring how to take a story or world into images, audio, video, and games—and sharing what we learn while we build. Your first step: leave a comment telling us what you want to make and what’s getting in your way. A book? Your first chapter? A world you can’t stop thinking about? Tell us about it. Glad you’re here. Let’s turn imagination into creation, without the slop. — Shane

Here are all 10 prompts from the video, ready to paste. Paste them into Claude or any coding AI, inside your game's project, and change the words in [brackets] to fit your game. Some steps need your engine's own tools for export, rendering and video, so your AI may need to adapt them. 1. ONE AI, ONE JOB Write a file called TEAM.md. List every part of this game: combat, world, story, art, menus, builds. Skip any part the game doesn't have yet. Give each part one owner and name the exact files that owner controls. If one file holds two parts, split the file or give it to one owner. Each AI I run gets this rule: you only change files you own. If you need a change in someone else's part, write the request in TEAM.md and leave their files alone. Add a line to the file my AI reads at startup (CLAUDE.md, AGENTS.md or similar) telling it to read TEAM.md first. 2. GIVE THEM A GROUP CHAT Set up a shared log file, CHAT.md, that every AI on this project reads and adds to. Keep it in one shared folder, and never on separate git branches. Before you start a job, add a line starting CLAIM, with the time, your name and the files you're touching. When you finish, add a line starting RELEASED, with what changed. Before you start anything, read the last 30 lines and also search the whole file for any CLAIM with no matching RELEASED. If someone else has claimed your files, leave them alone: pick something else, or ask me if that was the only job I gave you. If a claim looks abandoned, ask me before taking it over. 3. KEEP ONE RULINGS FILE Create RULINGS.md. When I clearly decide something, it goes in, in my words, with the date. If you can't tell whether I decided or was thinking out loud, ask. Where it disagrees with another document, the ruling wins. Don't edit my words. When I decide something new in this chat, add it, then show me the line. Add a line to the file my AI reads at startup (CLAUDE.md, AGENTS.md or similar) saying: read RULINGS.md before any other file.

Every tool an author pays for, in one place. This is the Author Cockpit: write, plan, check your voice, catch AI slop, research the market and format your book, all in one app. Our Skool is Free to Join. Check out Our Slop Detector Completely Free: http://stopslopstudio.com/detector/ See our list of the TOP FREE TOOLS for Authors: https://stopslopstudio.com/free-tools/ Get the full Cockpit with Stop Slop Premium - Only $20/month for founding members: https://www.skool.com/stopslop