holy sh*t
SpaceXAI (@bot) team showed their agent setup for engineering, design and marketing:
Lauren Tan (@poteto) - engineering
→ Dr. Eggbot
audit role boundaries, instructions and missing skills
→ Matcha
split work by dependencies, file ownership and acceptance criteria
→ Cloud agents
implement changes and run checks in the target environment
→ P Stack
evaluate skill revisions with Cursor cloud agents
run independent tasks in parallel. coordinate edits to shared files
Peng Zheng (@pengzheng_) - design + product
→ PM + designer + engineer
surface constraints and review trade-offs
→ Figma MCP
extend the reference screen using existing components
→ design-system skill
apply consistent typography, colors and spacing
→ Writer
refine voice and language
check loading / empty / error / success states before marking the flow complete
Matt Palmer (@mattyp) - marketing
→ Marketing Review
revise copy with the applied rule and rationale
→ Brand Tool Bot
retrieve brand assets, materials and presentations
→ Typefully API + editorial skills
prepare copy and proposed posting schedules
→ Slack routine
catch missed requests and duplicate work
validate account, timezone and posting time. require approval before live scheduling or publishing.
Save this to improve your multi-agent setup
Je pose ça là pour les courageux
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎Célibataire et à la recherche d'un date doux (et très audacieux)
︎
︎
︎
︎
︎
︎
︎
︎
︎
Alors
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎
︎T'as le niveau pour assumer ou pas ?
Lauren Tan’s pstack makes a lot more sense once you look at the bot team behind it.
she’s not using one “super agent” for all tasks.
instead, the work gets split across specialists:
• Chief of Staff → turns fuzzy goals into a plan
• Hatcha → research + synthesis
• Engineer bots → build, refactor, test
• Dr. Eggbot → review + catch weak assumptions
• Potato → keeps recurring work running
• Suki → UX, polish, final output
• Crumb → memory + context across long projects
the interesting part is the handoff:
goal → plan → specialists → review → final result
each bot has a narrow job, clear trigger, and expected output.
I mapped the whole team + delegation flow in one page below ↓