Brian Yip
422 posts

Brian Yip
@brianjyip
building paceline studios | offline @rugiethealth | odf26 past: @joinkudos @worklifevc @honey @meundies
Los Angeles, CA เข้าร่วม Haziran 2009
178 กำลังติดตาม619 ผู้ติดตาม

@youyuxi oh-my-pi has a Cursor integration
github.com/can1357/oh-my-…
English


@RadekTomsej @superset_sh Works for any CLI agents but we can add explicit pi support
English

At @superset_sh, we use the tool 10+ hours a day and build for our own use cases. I got a lot of questions on how to squeeze every last bit of performance out of the tool. So here's my setup.
I've seen much more insane setup from our customers and even within our team. This is just my personal preference. Share below if you do something different :)
Topics covered:
0:00 - Intro
0:30 - Sidebar and sections
1:14 - Bulk workspace creation
3:16 - Presets
4:03 - Changes and PR review
5:35 - Filetree
6:20 - Search
6:45 - Sections
7:08 - Tasks
7:55 - Agents configuration
9:00 - Settings and customization
English

Apparently the tmux that does NOT suck exists
It has an absolutely unpronounceable name and is called Zellij
I will try it now thanks everyone for recommending it 😊
zellij.dev/about/
GIF
@levelsio@levelsio
I hate tmux It's so incredibly user unfriendly The shortcuts make no sense I wish someone would make a better tmux Even just logging into tmux attaching the screen is an illogical hell to type Again I hate tmux, it's so shit
English

have switched to pi.dev as my agent harness. @badlogicgames has built something very useful.
what do folks like as an extension to manage multiple agents at the same time. something that would
- show me the status of various agents
- show me what is stuck
- run meta analysis to suggest better mechanisms (switch models, a side agent that can analyze the current agents)
might code one up if nothing exists.
English


Hard to expand a mission and sharpen a brand at the same time. Proud to be part of a team that just did. @RugietHealth



English

Migrated from @openclaw to Hermes Agent by @NousResearch this weekend and won’t be looking back
English

Pro Tip for FRONTEND DEVS:
> Don’t just “pick some Tailwind classes” and vibe.
> Build a real design system once, then reuse it everywhere:
- Define a small, strict set of primitives: colors, spacing scale, radii, typography, shadows
- Wrap them into components (button, input, card, modal, etc.) that you actually use across projects
- Document when to use which variant so your UI doesn’t feel random
> Then back it with tokens + a linter:
- Put all colors, spacing, font sizes, z-indexes into tokens (JS/TS, CSS vars, or Tailwind config)
- Add a custom linter / ESLint rule / stylelint rule that screams if someone hardcodes `#fff`, `16px`, or `margin: 37px`
- Fail PRs that don’t use tokens or try to sneak in one-off styles
Do this once and every new screen ships faster, looks consistent, and is way easier to refactor later.
English


















