Shan

North star

Build systems that help people move faster with confidence.

At work: make complex systems reliable, testable, and operable.

Outside work: keep refining practical AI and agent orchestration through fast iteration and shipping.

How I work

• Public by default. If it can help others and is not sensitive, it should be in-channel, not buried in DMs.
• Direct and clear. Cut fluff, get to the ask, and respect people's time.
• Async first for documentation and reuse. Sync when collaboration genuinely benefits.
• Meetings need value. I should be giving value or getting value I cannot get from notes, transcripts, or recordings.
• Feedback should be direct and honest: understand the why, then help unblock.
• Priorities: ownership and speed.

Current focus across work and outside-work systems.

• At work: full-stack delivery on payments, bridging, and staking with stronger testing, reliability, and docs.
• Outside work: shipping agent-first CLI tools and sharpening orchestration through real shipped products.
• Writing: sharing practical notes on what worked, what failed, and what changed.

• tfl-clilive

  Transport for London in your terminal. Live tube status, journey planning, arrivals, disruptions, and bike availability. Agent-first with automatic JSON output when piped.

  view project
• companies-house-clilive

  UK company data in your terminal. Search companies, directors, filings, ownership, and insolvency records via the Companies House API. Built for AI agents, still useful for humans.

  view project
• chaingreplive

  Grep for on-chain events. Point at a contract and block range, get decoded event logs streamed back. No indexer, no SQL, no setup.

  view live

• One Agent is Enough

  21 Mar 2026 · 7 min read

  Why most people don't need five agents talking to each other. Skills, crons, playbooks, and memory in a single-agent setup that actually works.

• Stop dodging the messy codebase

  14 Mar 2026 · 4 min read

  The rough codebases everyone avoids are where the real learning and visibility live. A recent dependency upgrade turned into a full cleanup and the team noticed.

• I built grep for on-chain events

  12 Mar 2026 · 5 min read

  I kept doing the same thing at work. So I built the tool I wanted and put it on the internet.

• › 2026-03-21: Added GitHub Action to auto-bump siteLastUpdated on every push to main.

• › 2026-03-15: Added chat/LLM integration to my personal site with rate limiting and prompt-injection guardrails.

• › 2026-03-14: Fixed and promoted a backend indexer by completing a secrets migration and validating production recovery.

• › 2026-03-13: Released my first backend service end-to-end, including debug, promotion, and observability flows.

• › 2026-03-12: Built a dump-to-briefing pipeline that turns daily notes into priorities and staff-eng prompts.