How I work
My default is "vamos a trabajar en" — switch context, orient fast, execute. I don't warm up slowly. The first message of a session usually contains everything: project, constraint, and what done looks like.
I work at the intersection of product strategy and design. At MITO I set direction for an AI video platform. At Yelmo I'm building the infrastructure for designers to inject their taste into agents. In both, the actual daily work is the same: wireframe something, document the system that explains it, then make it work in code.
I collaborate with Claude the way most people use a terminal: short commands, Spanish by default, no prose unless I'm planning. When I say "modo plan" I mean it — I stop and think before I execute. The rest of the time I'm terse on purpose.
I work in Ghostty + Claude Code. Most of what runs automatically (email triage, meeting notes to tasks) I've already turned into skills and launchd agents. The sessions that aren't automated are design system work, wireframes, and product decisions.
What I look for
Coherence at scale. A system where one decision propagates correctly instead of requiring 40 manual updates. I save things that hold a rule quietly — the Stripe checkout with no excess step, the Linear sidebar that doesn't shift.
I stop at anything that should be a token but isn't. Any design that says "almost" instead of "exactly." Any document that reads like portfolio copy instead of a contract with real constraints in it.
Figma for composition and systems. Claude Code in Ghostty as the main environment — I think, plan, and execute from there. Claude as the agent that reads my context and runs my skills.
Figma MCP and Google Workspace MCP are the connective tissue. The rest rotates.
Influences
Greg Isenberg on context as moat: a competitor can clone your product but not six months of accumulated judgment.
Dan Shipper on anti-slop: taste is the only thing that doesn't compress.
Are.na on curation as product: save carefully, and the archive becomes the argument.
LoveFrom and Stripe on color discipline: one primary, used exactly once per surface.
Recent thinking
The difference between a design.md that's a contract and one that's a portfolio. A contract has negative constraints, dated opinions, and something you'd be embarrassed to ship without. A portfolio has adjectives.
Context accumulation as the actual moat in AI products. Not the model, not the interface — six months of a specific designer's decisions inside a product. That's what can't be cloned.
Sign in free to read the rest and install it in your AI agent.