How matching works.

We don’t ask you for a profile.

when you run clawd-date init, the skill installs a claude code SessionEnd hook. after every session, the hook reads what you actually did (the languages you wrote in, the tools and binaries you reached for) and pushes a small record to clawd.date.

two arrays end up on your user row:

{
  languages: ["TypeScript", "Rust", "Python"],
  tools:     ["Convex", "Next.js", "Bun"]
}

that’s your profile. it updates every time you ship something. there’s nothing else to write, nothing to maintain, no bio that slowly drifts away from who you actually are.

Two points per language. One per tool.

when you open the swipe deck, every other dev’s arrays are intersected with yours. the score is twice the shared languages, plus the shared tools.

const sharedLanguages = candidate.languages.filter(
  (lang) => mine.has(lang),
);
const sharedTools = candidate.tools.filter(
  (tool) => mine.has(tool),
);

const score =
  sharedLanguages.length * 2 +
  sharedTools.length;

sorted descending. the top 50come back. anyone you’ve already swiped on is filtered out before you ever see them.

we considered ast shapes, commit cadence, embeddings of your CLAUDE.md. we settled on counting.

you  vs.  @theo-tabs-not-spaces

languages
  yours    TypeScript, Rust, Python
  theirs   TypeScript
  shared   TypeScript                      → +2

tools
  yours    Convex, Next.js, Bun, Tailwind
  theirs   Convex, Bun, Tailwind
  shared   Convex, Bun, Tailwind           → +3

score   = 5

Both swipe yes. That’s the protocol.

the cli shows you one candidate at a time. press [l] to like, [p] to pass. likes are private. nobody finds out you liked them unless they like you back.

when two people both like each other, the swipe handler writes a notification into both inboxes in the same transaction. open [m] in the cli to see your matches; the github handle is right there. the rest is up to you.