Experiments and small things.
Not client work. Open-source tools I use every day, plus side projects I built to understand a problem. Smaller in scope than the case studies on /work, but they show where my attention goes when nobody's paying me.
Things you can install.
Tools I built because I hit the problem myself, then published because someone else probably has it too. All MIT, all installable in one line.
reclaim
A developer-aware Mac cleaner. It finds the disk space taken by build caches, package-manager stores, IDE artifacts and stale project dependencies, then frees it behind a three-tier safety review — nothing is deleted without an explicit opt-in, and every apply run writes an audit log. My last full cleanup freed 98 GB.
csm
Claude Session Manager pins a Claude Code account per project the way nvm pins a Node version. Each client gets an isolated session via CLAUDE_CONFIG_DIR, so switching repos switches accounts — no logging in and out, no committing work under the wrong identity.
ghswap
Switches GitHub accounts in one command. It swaps all three things that decide who GitHub thinks you are — gh CLI auth, global git commit identity, and the HTTPS credentials in your OS keychain — together, because swapping only one of them is the usual source of "why did I just commit as the wrong person". Windows, macOS and Linux.
email-explorer
A fork of G4brym's self-hosted email client that runs entirely on a Cloudflare account — Workers, D1, R2, no server anywhere. My fork adds multi-provider outbound sending and an AI drafting feature. It's what runs my own professional inbox at roughly zero cost.
reclaim and csm ship through my own Homebrew tap, ImadRashid/homebrew-tap. Everything else lives on github.com/ImadRashid.
Things I built to learn.
Not packaged, not documented, not asking for users — just things I built to answer a question.
Laptop production host
Personal laptop running Coolify + Cloudflare Tunnel + Tailscale as a home-lab PaaS. Hosts several side projects at near-zero cost.
Trading-bot backtester
Event-driven backtester for testing strategies on historical data. Clean separation between data, strategy, and execution layers so nothing leaks future state into the signal.
MCP server experiments
A handful of Model Context Protocol servers for local workflows — quick plumbing to connect assistants to files, data, and build tools without re-inventing the glue each time.