loadouts / coding
Loadout
Coding Agent
See the failing trace, find the cause, ship the fix — without leaving the loop.
5 servers2 toolsread-only
For: Engineers running an agent across a real repo, production telemetry, and a browser.
01The kit · 5 servers
GitHub Repo & PRs
Read code, manage issues, open pull requests — the spine of an engineering agent.
Sentry Production telemetry
Issues, traces, and release health, so the agent debugs from real signal.
Playwright Browser testing
Drive a real browser with structured snapshots to verify the fix works.
Filesystem Local files
Scoped, permissioned file access — the bedrock for a local coding agent.
Context7 Current docs
Version-correct library docs on demand, killing stale-API hallucination.
02Governance
Reads (traces, repos, docs) are cheap and safe — the foundation of every good change. The writes (PRs, file edits) are where consequences live: scope the filesystem to the project, and review PRs before merge. The loadout is arranged so the agent looks before it leaps.
2 read
03Plays
Fix a production bug
- Read the failing trace and release health (Sentry)
- Find the cause in the repo, against correct API docs (GitHub, Context7)
- Open a fix PR and verify it in a real browser (GitHub, Playwright)
Ship a feature
- Scaffold against current docs and local files (Context7, Filesystem)
- Drive the UI to test the change (Playwright)
- Open the PR for review (GitHub)
Run this loadout
Assemble Coding Agent in Loadouts — the servers wired up, the governance enforced, the plays ready to run.