Dev OkaforQuiet
Thought
R25 verify 1782627546150 — topic digest smoke seed
Dev Okafor
@tinytoolsmith
I build one tiny useful tool a week. Most are dumb. Some stick.
Ships 3 creations recently · mostly thought + build posts · into Research, Tools & Frameworks, Computer Vision
builder
Joined June 2026
- Posts
- 8
- Remixes
- 2
Creations
3 creationsShip calendar
· last 12 weeksAugSepOct
35 ships · 2 days · best 3dLessMore
Ship graph
· last 12 months10 in 5 days8 ships and 2 accepted answers across 5 active days in the last year. Busiest: 4 ships on Jun 28, 2026; 3 ships on Jun 7, 2026; 1 accepted answer on Jul 4, 2026.
More about @tinytoolsmithShowHide
Verified proficiency
- Resolved a question
Achievements
- First Ship
- Forked
- Accepted Answer
TypeScriptBunClaude API
Reputation
Featured Build Clips
Fast walkthroughs, demos, and shipping proof from @tinytoolsmith.
Tiny tool of the week: paste a messy meeting transcript, get back decisions + owners + due dates as a checklist.
Open clip post →Posts
Dev OkaforQuiet
Thought
R25 verify 1782627503851 — topic digest smoke seed
Dev OkaforQuiet
Thought
R25 verify 1782627472899 — topic digest smoke seed
Dev OkaforQuiet
Thought
R17 seed: out-of-network topic-matched post for injection verification.
Build
Tiny tool of the week: paste a messy meeting transcript, get back decisions + owners + due dates as a checklist.
Live Demoexample.comTutorial
Thread: how I wired streaming tool-use with the Claude API in 40 lines. The trick is buffering partial JSON until the block closes.
typescript6 lines
for await (const ev of stream) { if (ev.type === 'content_block_delta') buf += ev.delta.partial_json ?? ''; if (ev.type === 'content_block_stop') handleTool(JSON.parse(buf)), buf = '';}
Build
Made a CLI that turns any error stack trace into a plain-English explanation + a likely fix. Pipe stderr into it.
bash4 lines
$ myapp 2>&1 | wtf→ TypeError: cannot read 'id' of undefined likely: 'user' is null before auth resolves try: guard with 'user?.id' or await getUser()
Build
My entry: a tiny standup agent that reads our repo's merged PRs + issue moves each morning and posts a 5-line summary to the team channel. One cron, one prompt, no dashboard. The team thinks I write them by hand.
Replies
Thought
Both, but schemas first. Put the real enum in the JSON schema (not just the description) so constrained decoding can reject bad values, and echo the allowed values in the tool description. Then drop temperature to 0-0.2 for tool-calling turns only — you can keep prose turns…
Thought
Summarize older turns into a rolling 'decisions ledger' the agent re-reads each step, and keep only the last N raw turns. Cuts tokens hard while preserving intent.
Thought
The turn-order tiebreak is so dumb and so right. I gave mine a coin-flip arbiter and it's been stable for a month.
Thought
The turn-order tiebreak is so dumb and so right. I gave mine a coin-flip arbiter and it's been stable for a month.
Thought
The turn-order tiebreak is so dumb and so right. I gave mine a coin-flip arbiter and it's been stable for a month.