Vibe coding packs, templates and launch reviews, page 2
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.
The hard floor: nine page checks before anything goes live (free sample)
Nine pass or fail checks that block publishing an agent-built page, the one truth rule, and a prompt that makes your agent check the real page in a browser.
Share one small kanban board with your coding agents through MCP
Kanzo is a tiny self-hosted kanban board with a built-in MCP server. Claude Code or Codex can take the next task, comment on it and move it, and its tool list costs roughly 800 tokens of context.
Keep an app's rules in one data file so the agent can change behavior without touching code
A builder made a 90s-style scrolling cable TV guide for Plex, Jellyfin and Emby with Claude. A written spec came first, all channel and schedule rules live in one JSON file, and later ports used the first app as the reference.
Judge agent-written libraries with test suites your side did not write
A team built open-source C# libraries with a factory of agents (planner, project manager, orchestrator, engineers, reviewers) and scored each one against public conformance suites such as test262 and html5lib, publishing the failures too.
Give agents reverse engineering output they can check, not guess
borer is an early open-source reverse engineering engine built for agents. It is one Rust binary that runs as an MCP server, keeps lists paged and capped, and checks decompiled C against the machine code in an emulator so the agent knows what is proven.
Have the agent build a tool that runs without it
After 30 days with an always-on agent, one user's main lesson was that repeated agent steps are fragile and costly, and the better result is a script or small app the agent writes once that then runs on its own.
Revive Old Tech with Coding Agents: drivers, firmware, crash patches and device bridges
A Markdown method for making abandoned hardware and old software work again with a coding agent: a REVIVAL.md brief, six revival lanes, ways to let the agent see the target, a closed build and read loop, a bug-to-check ledger, do-no-damage rules, a rules block and 14 prompts.
Eyes on the target and the bug-to-check ledger (free sample)
Seven ways to let a coding agent see what a device or old program is doing, a CHECKS.md ledger that turns every fixed bug into a build check, and two prompts.
Backends for Agent-Built Apps: pick a shape, write the contract, keep the data safe
A teaching guide for the server side of apps your coding agent builds. Pick one of five backend shapes with six questions, write a BACKEND.md contract the agent follows, and get migrations, sign-in, access rules, secrets, webhooks, jobs, free tier limits and live monitoring right. Includes a rules block and 14 prompts.
The six backend jobs and the access table (free sample)
The six jobs every backend does, a default-deny access table, two rules to paste into your agent's rules file and a prompt that tests access as three people.
Cross-Harness Relay: Grok Bot, Claude Code, Codex and Hermes on one job
A bot template and teaching guide for running more than one agent harness on the same work. Six seat cards (front desk, planner, builder, reviewer, tester, night shift), a RELAY.md seat map, a relay packet for every handoff, four loop shapes, routine-or-judgment routing with a fallback when limits run tight, a preflight check, the front desk and night shift split with a proof footer, shared memory rules, eight relay drills, a rules block and 14 prompts.
The relay packet and the routine-or-judgment table (free sample)
The packet every handoff between agents should carry, a table for which work can move to a cheaper or fallback agent and which stays with you, two rules to paste and a check prompt.
Agent Skills Workshop: write, test and run SKILL.md skills for Hermes, Claude Code and Codex
A bot template and teaching guide for building your own agent skills instead of collecting other people's. A skill card template, a three-skill split for long jobs (reference lock, plan with timings, build and critique), a loop that turns your corrections into skill drafts, an intake check for skills you did not write, four action classes, a SKILLS.md register, an overnight run sheet, eight skill drills, a rules block and 14 prompts.
The skill card and the three-skill split (free sample)
A SKILL.md card template with Done means, May not and an action class, the three-skill split for long jobs, two rules to paste and a check prompt.
Don't Get Sued: a pre-launch legal-risk gate for AI-built apps and agents
A read-only agent gate for the fourteen legal risks that hit small builders most: marketing texts and email, trackers before consent, accessibility, kids' data, biometrics, plain-text personal data, AI disclosure, AI claims you cannot prove, takedowns, policies that do not match the product, renewals and refunds, licenses, and agents that act for users. Evidence rule, gate register, seeded test app, 12 prompts, counsel packet. Not legal advice.
Two launch checks: trackers before consent and AI claims you can prove (free sample)
From Don't Get Sued: the read-only rules block, a check for ad and analytics scripts that load before any cookie choice, and a claims audit that sorts every AI claim on your pages by the evidence behind it. Not legal advice.