Become a sponsor to K Merchant

Why sponsor

I build local-first agent tooling — things a coding agent can run on a machine you control, no vendor lock-in, no paid API baked into the core loop — and I send the hard fixes back upstream when I find them.

What I ship in public

/reimagine-it — one agent skill, any file, a content-aware design leap

github.com/kazimrmerchant/reimagine-it · v2.2

Feed it a plain webpage, a PDF, a Word doc, a PowerPoint, a .mobi, an .epub, a code file, a protocol spec — anything. In one command it derives the palette, motifs, motion, and 3D from what your source is actually about and ships a rebuilt reading room. A Texas notebook comes out in navy / cream / red / gold with a Lone Star lockup and a west-Texas sunset shader. A marine-biology paper would come out in teal / kelp / bone / bioluminescence with a caustics shader.

• Nine tested case studies in the repo, every visual rendered locally from a real .html file. No CDN, no paid API, no third-party service.
• Open creative engine — same command on the same source samples a different reader register every run (dashboard-live / editorial-drift / field-guide-quiet / cinematic-shader / neubrutalist-blunt / poster-jazz-improv / data-humanist). Roughly 500–2,000 coherent draws per typical source. Pin one with --seed or --variant <letter>.
• Craft floor shipped in every output (v2.2): :focus-visible at ≥ 3:1 contrast, ::selection on-palette, prefers-reduced-motion decompose (not suppress), compositor-only motion (transform/opacity only), animation-timeline: view() for scroll motion, INP < 200 ms, CLS = 0. Distilled from ~150 sources — Vercel's interfaces, Linear's design engineering, WCAG 2.2, the 2025 Awwwards SOTY nominee stack, Instrument, Active Theory, Locomotive.
• Real WebGL2 shader hero in the flagship demo — inline fragment shader, single .html file, no vendor folder, no external font fetch.

book-guide-mcp — playbooks and tutors your agents run locally

github.com/kazimrmerchant/book-guide-mcp

MCP server for Cursor, Claude Code, VS Code, and any client that speaks MCP. Cite books you own; no API keys required for the core loop.

research — dated public notes on local-first agents and MCP

github.com/kazimrmerchant/research

The failure modes that show up when tools actually have to run, not the polished after-the-fact write-ups.

Upstream — hard, reviewable work (not drive-by typo farms)

Open PRs on projects I use every day: simonw/llm, pypa/hatch, and more coming. Each diff is human-reviewed, tested with the project's own suite when available, and disclosed per each project's AI-usage policy. I own every line.

How sponsorship helps

Sponsorship buys focused time for:

1. New /reimagine-it domains, form packs, and locks — sponsors get priority on custom domain packs and roadmap input
2. Harder upstream bugs and capability upgrades on the Python tools I contribute to
3. Polish and docs on public agent tooling so more devs can adopt it
4. Honest build-in-public updates — no fluff dashboards, just the shipped diff

Honest expectations

I use AI coding agents to move faster. Every public contribution is reviewed by me, verified with the project's own tests when available, and I can walk through the diff line by line. Private commercial products stay private — sponsors support the public work.

Thank you for considering a sponsorship.