Prompt packs for builders, game devs and solo founders, page 7
Tested prompt sets with [placeholders] you fill in, rules that keep the model honest, and a clear stop point before anything irreversible. Two prompts from every pack are free to read on the page.
Vet Before You Install: twelve checks, a sandbox recipe and a tested vetting folder for third-party agent code
Decide whether a skill, plugin, mod, MCP server, connector, repo or model gets into your agent setup: sort the seat, read every file that runs, map reach and the data path, pin and vendor it, trial it in a sandbox with a planted fake key, then record a decision the owner approves at their own terminal. v1.1 adds a seat sort before any vetting, two new checks (data path and reach, approval surfaces), evidence tiers, twelve token classes including hidden text, encoded strings, startup file edits and approval hooks, a fresh-session second read, data path questions for proxies and routers, dependency and model weight pinning, a fifth decision (not vettable) with recheck dates and an approved shelf, more special cases, a vetting folder with a fifteen-check read-only checker and an owner approval helper, agent files for Grok Bot, Claude Code, Codex and Hermes, and twelve new prompts (27 in all). Price unchanged.
Vet Before You Install: the twelve checks (free sample)
The seat sort and the twelve checks to run before any third-party skill, plugin, MCP server, repo or model touches a real machine, plus one prompt and the decision line. Updated to v1.1.
Grok Bot Templates: personas, standing orders and handoffs
A Markdown pack for setting up Grok Bots that do useful work on a schedule: 8 ready-to-paste personas, standing order cards for scheduled routines, event routine recipes, multi-bot handoffs with a decision log and four approval gates, memory rules and a test set.
Standing orders for a scheduled Grok Bot (free sample)
The card we use for every scheduled Grok Bot job, a cron table in local time, and two reporting rules (quiet by default, end of day) that cut most of the noise.
Governed Agent Teams: subagent personas, authority maps and handoffs
A Markdown pack for running a team of coding and research agents with clear limits: 7 subagent personas for Claude Code with Codex AGENTS.md and Hermes skill versions, a Desk Authority Map, three role risk classes, a handoff packet the receiver verifies, an evidence standard, a decision ledger and a reach inventory.
The Desk Authority Map for agent teams (free sample)
One template that says what each agent may do without you, what it must ask for, what it never does and what proof it owes, with an example row and an audit 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.
Game Dev with AI Agents: method, prompts, skills and check loops
A Markdown playbook for building games with Claude Code, Codex or Claude: a seven-stage method, a staged brief, 16 prompts, five agent skills, self-check loops, engine notes and 30 game concepts.
Make your agent play the game before it says done (free sample)
One rule, one playtester skill and a play log template that make Claude Code or Codex test your game with real controls before reporting done.
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.
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.
Write patch notes and store page copy players actually read
16 prompts that turn your commit log or task board into patch notes, a Steam or itch.io store page and devlog posts in your own voice, with every line tagged to the change it came from and a read-only checker that flags missing, invented-from-nothing and internal items before you post.
Price, pitch and follow up: prompts for solo founders selling services
15 prompts for pricing a service, writing a one-page offer and proposal, handling objections and following up on a schedule, plus a read-only checker that flags a price under your own minimum, numbers that are not in your notes and which follow-up is due for each lead.
Pre-launch security prompts for vibe-coded apps: Supabase RLS, leaked keys and open doors, with two checks you can run yourself
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. Version 1.1 adds two read-only checks you run yourself: rls_check.sql, which logs in as the public key and as a second user to prove a stranger cannot read your rows, and bundle_scan.py, which finds secret keys in your production build, including a service role key grep cannot see. Both were tested on a made-up app with planted problems.
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), an Approvals section that makes the agent stop and wait for your yes, a table of what Grok Bot, Claude Code, Codex, Hermes and Cursor each read, a read-only checker for your rule files and 9 prompts to write, trim and test your own.
Ask-first rules for AI agents: hard nos, approval cards and a test set
Paste-in rules that make an agent ask before it sends, spends, posts or deletes, define what a real yes is, and stop retries after a no, plus 12 test scenarios to check it.
Build a writing style guide your agents can follow
Ten prompts and a template that turn 20 to 40 messages you really wrote into a one-page STYLE.md, so drafts from any agent sound like you and stay drafts.
Start free. Buy a file. Or have it built for you.
Free samples
Read and download in full. No signup.
Marketplace
Packs, templates, prompts and bots. One-time checkout, instant download.
Agency AI operations
Built, installed and managed. Growth Fleet starting at $2,500 setup + $750/mo, Managed Ops starting at $5,000/mo.