Skip to content

Tag

Vibe Coding

5 agents tagged Vibe Coding. Related agents on each page prefer a shared tag before they fall back to the same shelf.

Swipe sideways

  1. Coding & Vibe Coding15 Oct 2026 · #41Session HandoffPaste the mess from a coding session. Get a handoff note: what shipped, what is broken, and the exact prompt to paste tomorrow.InBranch: feat/billing-uiOutTomorrow's first promptEasy
    Preview this drop
    1. 0:00 The swampBranch feat/billing-ui. Auth works. Billing page half done. Stripe webhook returns 400. Receipt email never fires.
    2. 0:08 What actually shippedLogin on staging, pricing table render, stripe package installed. Plan change is still a stub. PayPal left alone on purpose.
    3. 0:16 What is brokenWebhook 400, missing signature check, BillingForm customerId null, receipt email not wired. Ranked by what blocks the rest.
    4. 0:24 Tomorrow's first promptA paste-ready prompt that starts at the webhook 400, forbids touching PayPal, and asks for a signature check plus a failing test.

    No daily video for this drop yet. The in and out lines above are the preview.

  2. Coding & Vibe Coding29 Sep 2026 · #25Env Var AuditorPaste .env.example and the code that reads it. Get missing keys, unused keys, and names that look like live secrets.In.env.exampleOutThe fixMedium
    Preview this drop
    1. 0:00 The driftPORT and DATABASE_URL are read. DATABASE_URL is required. FLY_REGION is read and missing from the example.
    2. 0:08 UnusedNothing in the example is unread. FLY_REGION is the gap, the other way.
    3. 0:16 The live-looking valueSTRIPE_SECRET_KEY's example starts with sk_live_. That prefix does not belong in an example even if they say it is fake.
    4. 0:24 The fixAdd FLY_REGION=local. Change the Stripe example to a sk_test_ placeholder. Do not print a real key.

    No daily video for this drop yet. The in and out lines above are the preview.

  3. Coding & Vibe Coding17 Sep 2026 · #13Test Plan from the PromptPaste the prompt you used to vibe-code a feature. Get the checks to run before merge, including the case that prompt forgot.InPrompt I gave Cursor:OutLaterMedium
    Preview this drop
    1. 0:00 The original promptA refund button for paid orders under 7 days, a POST, and a success toast. No failure, no double click, no permissions.
    2. 0:08 The forgotten casesA 500 from the API, a second click, an order already refunded, and a viewer who is not allowed to refund.
    3. 0:16 Before mergeThree checks: the happy path you asked for, the failed POST does not say Refunded, and a double click does not send two POSTs.
    4. 0:24 LaterThe 7-day boundary and the hidden button are listed as follow-ups, not pretended to be done.

    No daily video for this drop yet. The in and out lines above are the preview.

  4. Learning12 Sep 2026 · #08Explain Like I'm ShippingLearn a concept by making the model explain the smallest version you could ship this week, then quiz the gap.InConcept: idempotency keys on a POST that creates an invoice.OutThe quizEasy
    Preview this drop
    1. 0:00 The constraintA TypeScript billing API, Postgres already there, one afternoon, no consensus lecture.
    2. 0:08 The tiny versionA unique key column on invoices, the client sends it, a retry with the same key returns the same invoice row.
    3. 0:16 Left outNo new queue, no vendor, no lecture about exactly-once delivery in the abstract.
    4. 0:24 The quizThree questions: where the key is stored, what a second POST returns, and what you do if the key arrives empty.

    No daily video for this drop yet. The in and out lines above are the preview.

  5. Coding & Vibe Coding5 Sep 2026 · #01Diff Risk ReviewerRead a vibe-coded diff for behavior risk: what changed, what can break, and which check to run before you push.Indiff --git a/app/api/orders/route.ts b/app/api/orders/route.tsOutThe checkMedium
    Preview this drop
    1. 0:00 The intended changeOne sentence: checkout should trust the price the server already computed.
    2. 0:08 The hunk that movedThe reducer that summed item.price * qty is gone. total now comes from body.total.
    3. 0:16 The riskA client can post any total, including zero or a negative, and the route marks the order paid.
    4. 0:24 The checkSend the old cart fixture and assert the stored total matches the server sum, not the body.

    No daily video for this drop yet. The in and out lines above are the preview.

Tomorrow's drop

Get the daily agent

One email when the drop goes up. The same list as the signup on the page.