AX⚡️DX High voltage dev workflows
summary
Claim: agent experience (AX) is a discipline not a checkbox and directly shapes developer productivity. Practical steps are: audit which agents teams use; add context files (agents.md, steering files, cloudmd) and core dependency docs; run agent evals against repos; create shared subagents as markdown and centralize globals in a repo plus a CLI. Ephemeral preview environments, knowledge graphs, and feedback loops tighten correctness and reduce hallucination; these techniques prove effective on real codebases.
AI-written summary · about
chapters (9)
- 0:00Introduction and keynote setup
- 1:12Agent experience vs developer experience
- 6:09The one-person band problem
- 8:16Crawl walk run for agent experience
- 12:10Context files and dependency docs
- 16:24Knowledge graphs and feedback loops
- 20:41Shared sub-agents and distribution
- 24:14Centralizing agent rules
- 26:24Agent evals and future steps
related talks
01mThe Agent Experience (AX): Preparing for the Next 100M Developers
19mFrom DX to AX
30mThe Rise of Agent Experience (AX)
15mAX is the only Experience that Matters
33mAgent Experience
25mAX is the only Experience that Matters
21mBest practices are trapped in your head and your AI has no idea
22mDX for Internal Teams