Vibe Code for Good · for the people closest to the harm

Codein serviceof one life.

A home for people using software to reduce harm and grow prosocial connection. Across gender-based violence, child safety online, radicalization, youth mental health, addiction, climate grief, and the loneliness underneath all of it. The first instrument is the Field Guide: it turns a cause into a behavior-first build plan, written in the voice of someone who has to live with the outcome.

Six questions · roughly four minutes · a document worth defending.

scroll
The thesis

We are not optimizing for engagement.

We are designing for behavioral change.

For prosocial connection. For lives less alone.

For the person before the worst version of their week arrives.

Most product tooling assumes you're growing a SaaS. Vibe Code for Good assumes you're trying to interrupt a harm or grow a connection. The output isn't a roadmap. It's a guide your team can argue with, share with a clinician, hand to a designer, and revisit when a build starts drifting away from the person it was supposed to serve.

Three commitments
i.

Specificity over scale

A guide written for one person is more useful than a strategy written for a population. Scale is what happens after the first life is right.

ii.

Behaviors over engagement

Time on app is not the goal. The goal is the phone call made instead of doomscrolling. The friend texted instead of disappearing. The pause before the post.

iii.

Harm prevention, intervention, and reduction at the core

Every guide names the failure modes you refuse to ship: contagion, grooming, surveillance of survivors, public humiliation, predatory monetization. Refusal is part of the design.

The method

Five movements, one quiet document.

  1. 01

    Name the person

    Not a persona. A specific human, in a specific week of their life.

  2. 02

    Define the win

    A sentence so small it's defensible. So real it's testable.

  3. 03

    List the behaviors

    Three to five visible moves. The choreography of the change.

  4. 04

    Refuse the harms

    Two or three failure modes you will not ship, even under pressure.

  5. 05

    Pick the pulse

    One number. One question. The honest signal you'll review monthly.

Worked examples

Three guides, three causes.

Load any of these into the Field Guide to see the shape of an honest answer. Edit, replace, or scrap them entirely. They're a starting posture, not a template.

Prosocial young men

Reaching boys before the algorithm answers first

For teams working on toxic masculinity, manosphere drift, and the loneliness underneath both.

Intimate partner violence

A safer first step for someone leaving a controlling relationship

For advocates building tools that have to be quiet, leave no trace, and assume the device is being watched.

Youth mental health

Holding a teenager through the longest hour of the night

For crisis teams designing for the moments between a hard thought and reaching out for help.

The first instrument · Field Guide

Six questions. One life.A guide that refuses to be generic.

Answer slowly. The output is only as honest as the inputs. If you'd rather feel it first, load any of the worked examples above.

01 — The person

Who, exactly, are you building for?

One person. Not a segment, not a cohort. Someone you could picture across a table.

01 / 06