//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
Profile
Loading...
Med-Peds ID Fellow Doing EHR Informatics Research | Driven by data, music, bicycle | Thoughts & typo-planting skill my own
Bennett Waxse








Loading...
I wrote up my approach in a blog post: bennettwaxse.com/blog/bioinfo... If you're a researcher curious about Claude Code, here's where I start. If you have a different workflow, I'd love to hear about it.
Why bother? Because LLM context windows are big enough to hold an entire project—so use them. Don't hide how you derived a cohort when that derivation can inform what you're asking the model to do next. 3/
- #CLAUDE.md files that orient Claude to your project's structure, conventions, and domain quirks - Reference materials (data dictionaries, trusted queries), so the model knows what's actually in your tables - .claudeignore to prevent reading secrets, redundant files, or data you shouldn't share 2/
I've been using #ClaudeCode for #research #informatics—cohort building, debugging pipelines, genomics in #AllofUs. Before any of that was useful, I had to set things up right. The setup isn't complicated, but it matters. Here's how I do it: 1/