Cha Khan · From the talk “It Just Keeps Getting Faster”, 19 Oct 2026
AI Resources
What I use every day to build with AI agents, in the order a piece of work goes.
Talk to your agent
Wispr Flow
EnkeonAgree on what to build
Grill Me
HTML, not MarkdownBuild it right
pstackHTML, not MarkdownMake it look good
taste-skill
Impeccable
diagram-designSee the work
HTML, not MarkdownELI5
Lavish
i-have-adhdAXI
agent-browserShip it safely
no-mistakesRun many agents
firstmate
T3 Code
herdr
Or hand it to your agentIt asks what you build and installs what you pick.
Read resources.md and walk me through setting these up. Ask before you install anything.Talk to your agent
Wispr Flow
Talk to your agent instead of typing. Messy is fine.
Wispr
Talk to your agent
Enkeon
One memory for you and all your AI tools. Context carries across sessions.
Enkeon
Agree on what to build
Grill Me
The agent interviews you until it understands what you want.
Matt Pocock’s skills
Build it right
pstack
Makes the agent work like a careful senior engineer, and prove it.
Lauren Tan (poteto), Cursor
Make it look good
taste-skill
Art direction and reference images instead of generic AI pages.
Leon Lin
Make it look good
Impeccable
Critiques and polishes any interface: layout, type, colour, motion.
Paul Bakaus
Make it look good
diagram-design
Plain words in, a clean diagram out. 44 diagram types.
Cathryn Lavery
Agree on what to build · Build it right · See the work
The Unreasonable Effectiveness of HTML
Ask for an HTML page, not a wall of Markdown.
Thariq Shihipar, Claude Code team
See the work
ELI5
Any topic as a picture explainer: big visuals, few words.
Thariq Shihipar, Claude Code community plugin
See the work
Lavish
An editor for your agent’s HTML pages. Click, change, send it back.
Kun Chen
See the work
i-have-adhd
Your agent leads with the answer and the next step.
ayghri
Great question! Let me think about this. Your auth flow has a few moving pieces: the middleware, the token verification, and the cookie handling. Looking at src/auth.ts, the verifyToken function (around lines 42-58) seems to be using an older jsonwebtoken API. One approach would be to update the package and rewrite that function. After making the change, you'd want to run the auth tests to confirm nothing breaks. By the way, you might also want to look at your dependency versions overall. Hope this helps! Let me know if you want to dig deeper.
Edit src/auth.ts:42 to update the token validation. 1. Open src/auth.ts 2. Replace verifyToken (lines 42–58) with the snippet below 3. Run npm test -- auth.spec.ts Next: paste the first failing line if any test fails.
See the work
AXI
Command-line tools built for agents: GitHub and Chrome, fewer tokens, fewer mistakes.
Kun Chen
See the work
agent-browser
Your agent opens, clicks and screenshots a real browser to check its work.
Vercel Labs
- openagent-browser open localhost:3000
- snapshotreads the page: buttons, links, fields
- clickagent-browser click @e3
- screenshotagent-browser screenshot page.png
- checkthe agent looks, then fixes what is wrong
Ship it safely
no-mistakes
Make no mistakes.
Kun Chen
Run many agents
firstmate
Talk to one agent. It runs a crew and checks their work.
Kun Chen
- yousay what you want, once
- firstmateplans and splits the work
- crewagents build the parts in parallel
- checkevery part is reviewed
- shipmerged, you get one report
Run many agents
T3 Code
One app for Claude, Codex, Cursor and more, side by side.
Theo, ping.gg
Run many agents
herdr
A terminal where many agents run in panes you can watch and talk to.
herdr
