Hey Product Hunt! I'm Prem, and I built rp1 because I was tired of the same loop: try a prompt, watch my AI coding assistant go sideways, tweak it, repeat. Sound familiar? The core insight was simple: **most prompts that work well for coding tasks follow recognizable patterns**. Requirements gathering, design thinking, implementation strategy, code reviewthese aren't mysteries. They're workflows that experienced developers already know. So instead of reinventing these patterns every time I opened Claude Code, I packaged them into slash commands. **What RP1 actually does:** - `/knowledge-build` scans your codebase and creates context the AI can reference. No more "what framework are we using?" questions. - `/feature-requirements` -> `/feature-design` -> `/feature-build` -> `/feature-verify` gives you a complete development workflow, each step building on the last. - `/pr-visual` transforms PR diffs into Mermaid diagrams so you can actually see what changed. - `/code-investigate` does systematic bug hunting instead of random guessing. - And a whole lot more of QOL workflows like /pr-review, /code-comment-cleaner etc. All of these run in a **single pass**. No agent loops that spiral into nonsense. Each command uses constitutional promptinga structured approach that keeps the AI on track without babysitting. **Why open source?** Developer tools earn trust through transparency. You can read every prompt, customize workflows for your team, or contribute back. Apache 2.0 license. **Currently supports Claude Code and OpenCode**, with Cursor, Goose, and Amp in the works. I'd genuinely love to hear: - What dev tasks do you still struggle to get AI help with? - What workflows would you add to rp1? Try it out, break it, tell me what's wrong. That's how this gets better. GitHub: https://github.com/rp1-run/rp1 Docs: https://rp1.run

Ready Player One (rp1)

Battle-tested workflows for Claude Code & OpenCode

Battle-tested workflows for Claude Code & OpenCode