Add exponential backoff to the retry loop in `Sources/Sync/SyncWorker.swift`. Start at 250 ms, double each attempt, cap at 8 s, 5 attempts max. Pin the schedule with a unit test. Constraints: don't change the retry function's signature.
What was said
okay so what I want you to do is um in the sync worker file that's in sources slash sync slash sync worker dot swift there's a retry loop and right now it just retries every hundred milliseconds forever basically and I want that to be exponential backoff so start at two fifty milliseconds double it each time cap it at eight seconds and give up after five attempts um and write a unit test that pins that schedule oh and don't change the retry function's signature because the the upstream client calls it and I don't want to touch that in this change
What this style writes
Review how the existing endpoint is defined in `api/org-settings.ts` and determine whether it's cleaner to add a new batch endpoint taking a list of org IDs or to add an optional `ids` parameter to the existing endpoint. Constraints: don't write the code yet.
What was said
so the problem is the dashboard makes like forty calls to get org settings in a loop um I think the fix is to add a batch endpoint that takes a list of org ids and returns them all at once and then change the dashboard to call that once instead uh actually wait I'm not sure if we want a new endpoint or just add an optional ids parameter to the existing one can you look at how the existing endpoint is defined in api slash org settings dot ts and tell me which is cleaner before you write anything don't write the code yet
What this style writes
Add a `--dry-run` flag to the backfill script at `tools/backfill.py`. Log every row it would write with the same format as the real writes, but not actually write anything. At the end, print a count so I can compare it to the select.
Constraints: don't add any other flags, don't refactor the script.
What was said
um can you add a dash dash dry run flag to the backfill script it's tools slash backfill dot py it should log every row it would write with the same format as the real writes but not actually write anything and uh at the end print a count so I can compare it to the select don't add any other flags and don't refactor the script I know it's ugly
Hear it in your own words
Say something and this style writes it up. No account, nothing installed.
Inside this style
Tone
Match my toneCasualBusinessFormalMatch my examples
Tone: the speaker's own. Change: nothing about formality, warmth, or attitude. Keep: their contractions, slang, asides, and exactly how direct or polite they were.
Editing
MinimalPolishFull reworkCustom
Editing: full rework into a brief an engineer could hand to a colleague. Change: reorder into goal, then constraints, then steps; merge repeats; cut the thinking-out-loud and the half-formed alternatives I talked myself out of. Keep: every constraint, file, identifier, number and "don't" exactly as spoken, and every open question as a question. Never resolve a question for me and never add a step I didn't ask for.
Instructions
7 on
Say Scriber starter
Write numbers as digits (3, not three).Say Scriber starter
Put anything I said "don't" or "never" about on a final line that starts with "Constraints:".THIS STYLE ONLY
When I mention a file, keep the full path I said, even if it's long.THIS STYLE ONLY
Adapt to the app I'm in🔒 GENERATED PER DICTATION
{You're writing in <app> — <its one-line description>. Match the norms of that medium.}
Writing examples
The creator's own writing, which the style learns from.
Add exponential backoff to the retry loop in `Sources/Sync/SyncWorker.swift`. Start at 250 ms, double each attempt, cap at 8 s, 5 attempts max. Pin the schedule with a unit test. Constraints: don't touch the upstream client, don't change the public `retry(_:)` signature.
Rename `legacyExport` to `csvExport` everywhere it appears, including the migration comment. Run `make test` after. Constraints: don't rename the database column, that's a separate migration.
Everything this style adds is above. The locked core rules run first for every style and are never part of a listing. Add it and all of this is yours to edit.
Notes from priya-ships
Most of my day is now talking to a coding agent, and the bottleneck moved from typing to explaining. This style is what I dictate into the agent's prompt box after I've looked at the code and know what I want.
It reworks my thinking-out-loud into a brief a colleague could act on: the goal first, then constraints, then steps. Things I said "don't" about end up on a final Constraints line, because an agent will cheerfully do the thing you mentioned in passing unless you fence it off. Open questions stay as questions; it never resolves one on my behalf.
File paths, function names, flags and error messages are copied verbatim in backticks. That matters more here than anywhere else: an agent will happily go looking for `handleRetry` when you said `handleRetries`, and it will find something.
It is deliberately not a scope-expander. If you dictate two things, you get two things. Numbers come out as digits so "retry three times" reads as "retry 3 times" in the brief.
Works well with the AI tooling dictionary, which fixes "cloud code" and "curser" before they reach the brief.
Recommended dictionaries
Picked by the creator to go with this style
AI tooling namesRecommended
Model and tool names spelled the way their makers spell them: Claude Code, Cursor, Ollama, MCP, LangChain, Hugging Face.
Anthropic · Claude · Claude Code · Codex · Copilot · Cursor