Vibe coding packs, templates and launch reviews
For people who build software by describing it to an AI coding tool: security prompts before launch, instruction files your agent follows, MCP setup, debugging without spiraling, and a review before real users arrive.
Debug a vibe-coded app without breaking it further
12 prompts that make your AI coding tool find the real cause of a bug, change one thing at a time and prove the fix before it moves on.
GitHub release notes bot: draft notes from merged pull requests
A GitHub Action that collects merged pull requests when you push a version tag, groups them by label and opens a draft release with notes written for users.
Turn a spreadsheet you run by hand into a small web app
A staged plan and prompts for turning the spreadsheet your team edits by hand into a web app with logins, forms and an import of your existing rows.
App Launch Check: a launch review for apps built with AI
Send a repo URL and get a scored report on deploy, domain, payments, legal pages, security basics and AI code mistakes, with a fix list in priority order.
Pre-launch security prompts for vibe-coded apps: Supabase RLS, leaked keys and open doors
14 prompts that make your coding agent find exposed keys, tables without row level security, open buckets and unverified webhooks in your own app, then fix them one commit at a time.
AGENTS.md, CLAUDE.md and Cursor rules starter files
Six fill-in instruction files for coding agents (base, Next.js plus Supabase, FastAPI, browser game, CLAUDE.md pointer, scoped Cursor rules) and 8 prompts to write, trim and test your own.
MCP server setup playbook: connect your agent to real tools without handing over the keys
Pick the fewest MCP servers for a job, check them before installing, scope the credentials, configure five clients, test with MCP Inspector and build a small read-only server of your own.
The Launch Bundle: every prompt pack and playbook in the store
All 5 prompt packs and all 7 playbooks in one .md file: security, agent rules, MCP, game launch, GPT migration, agent ops, pricing, patch notes and more, for less than half the separate price.
Token saver: keep long command output out of your coding agent's context
Two shell scripts and one rule line that make Claude Code, Codex, Cursor and other agents read a one-page summary of builds, tests and searches instead of thousands of lines.
Have your coding agent run a release gate before App Store submission
An indie developer who builds everything with agents shares the pre-submit checks his agent runs, what they caught, and why Apple still rejected his Codex-built puzzle game.
Review agent-written code in layers the way the Claude Code team does
The Claude Code team described how they moved most code reading to automated reviewers, kept humans for risky and directional calls, and still cut the share of reverted pull requests by more than 40% while merges doubled.
Pass a quiz on agent-written code before you push it
Sphinx is a free Git hook that pauses pushes to protected branches and asks you a scenario question about the diff your agent wrote, so you only release code you actually understand.
Improve a generated 3D scene with a screenshot and critic agent loop
A creator built a rainy neon city as a single 52 KB HTML file on WebGPU in about 40 minutes, and credits the quality jump to a loop where Claude screenshots its own render and a fresh critic agent reviews it.
Run a pool of coding agents that only merge fixes proven red then green
A maintainer ran a small office of Claude Code workers against 13 Rust repos for five days and got about 170 pull requests merged, then open sourced the tool as ApolloOffice.
Vibe Coding with AI Agents: method, prompts, skills and checklists
A Markdown playbook for building real software with Claude Code, Codex or Claude: a seven-step method, project file templates, 18 prompts, five agent skills, release and hardware checklists, cost notes and 24 project ideas.
Hand off agent sessions with decision logs (free sample)
Two small files and one skill that let a fresh Claude Code or Codex session pick up the reasoning behind your code, not just the code.
Let Claude Code run a sky camera through an MCP server that carries its own rules
An open-source meteor camera that Claude Code operates through an MCP server. The server hands the agent its own how-to skills and enforces the safety rules itself, so the agent cannot talk its way past them.
Vet Before You Install: ten checks, a sandbox recipe and a skill for third-party agent code
A Markdown pack for deciding whether a skill, plugin, mod, MCP server or repo is safe to let into your agent setup: read it first, pin and vendor it, trial it in a sandbox with a planted fake key, then write the decision down.
Vet Before You Install: the ten checks (free sample)
The ten checks to run before any third-party skill, plugin or repo touches a real machine, plus one read-first prompt.
Spec-First Build Docs: PRD, design system, architecture note, agents guide and readiness check
A Markdown pack of the four documents to write before an agent builds anything, sized to the stakes: a PRD an agent can build from without inventing scope, the smallest design system that holds, a one-page architecture note with reversal costs, an agents guide with a project tree for Claude Code, Codex and Cursor, a weekly staleness pass and a nine-area readiness check.
The one-page spec for an agent build (free sample)
Four questions to answer in ten minutes before a coding agent writes a line, as a SPEC.md template with four rules and a check prompt.
Agent Cost Levers: cut cost per solved task without cutting quality
A Markdown pack that measures what your coding agent spends per finished task, then works five levers one at a time: thinking depth, context curation, direct tool routing, cache and reuse, and a verified stop. Includes a baseline sheet, a rules block and 10 prompts.
Cost per solved task: the one-sheet agent cost check (free sample)
The one number to track for agent spend, a usage sheet, three rules for testing a change and a prompt that compares two runs honestly.
Front-Door Review Stack: catch machine-made tells, UX breaks and invented claims before a page goes live
A review gate for agent-built landing, pricing, product and profile pages: a hard floor that blocks publishing, a truth pass for every claim, 20 UX principles as yes or no questions, 36 machine-made tells with fixes, a real browser pass and a fresh-eyes reviewer.
Questions
What is vibe coding?
Building software mainly by describing what you want to an AI coding tool such as Cursor, Claude Code, Codex, Bolt, Lovable or Replit, then steering, testing and fixing what it produces.
Do I need to be a developer to use these?
No, but you need patience and git. Every item lists its difficulty, and the beginner items assume you can open a terminal and follow steps.
How do I know my vibe-coded app is ready for users?
Check deploy, domain, payments, legal pages, basic security and leftover AI mistakes. App Launch Check reviews all six and gives you a fix list.