i'm pooria. i build software that ships.
i build small software for people and agents, then write about what works.
- google search clicks
- 9
- google search impressions
- 317
- npm downloads
- 36,689
- npm downloads
- 16,322
- github stars
- 5
last 28 days
last 28 days
all time
last 28 days
across public repos
from google search console, npm and github, to 2026-10-07. updated daily. npm counts skip publish days, when mirrors and scanners pile on.
four things i built and shipped
a small set of repeatable choices
one capability, several doors
the web interface is for people. the api, cli, and mcp tools give agents the same useful work.
one stack, reused on purpose
next.js on cloudflare, d1 for data, r2 for files, and queues for slow jobs. lessons move between products.
the person keeps the final say
replytosocial drafts and waits. the useful automation handles repetition without taking away judgment.
the work is only part of the week
showing up 
getting outside 
between builds
the ones i actually get
why build several small products?
each starts with one repeated problem. shared infrastructure lets me test a narrow idea without rebuilding everything.
why does each product have agent tools?
agents should not need to click through a screen built for people. useful work gets an api, cli, or mcp tool too.
can you look at what i am building?
yes. send one paragraph and a link through the contact page. no deck is needed for a first reply.
what shipped. what broke. what changed.
one email when there is something useful to say.