Product designer for AI and MCP-first products. I design onboarding, activation and upgrades for people and their agents. Prev @twitter @uenodotco @palantirtech

dallas
Joined December 2020
I bet @paper would be an amazing story boarding tool for motion sequences 🤔
My timeline's full of one-shotted Opus 5.5 motion reels, all looking like the same slop. So I spent 2 days directing one, every frame and transition: full storyboard, clear motion instructions, real thinking behind each choice. Lovely result, sharing soon 👀
1
3
459
I've spent the last year designing for companies whose core products are an MCP/connector. It's an exciting new challenge onboard and activate users in this new environment. Here are four simple learnings I've had along the way
1
2
253
I'm in love with @paper. It's the best "code-to-design" and "design to code" tool right now. It feels so natural to: - Riff on ideas in paper - Push pixels for a bit and dial details - Ask agent to implement the design Overall amazing tool. Would love to have components though 🤞
2
11
656
The shape is portable. I run the same loop for trip planning, product research, content ideas, even sourcing UI inspiration. Pick the cadence. Point it at the topic. The artifact shows up while you're doing something else. Now go set up something similar and make your partner feel like your on top of planning date nights and family fun ❤️
247
My custom, always-on agent is the most valuable piece of software I own. We're in a beautiful DIY moment for software/tools. Every conversation, every workflow I wire into it, it gets more uniquely mine. You can't buy this... If you haven't started one yet, you should.. it's a massive unlock. Here's how mine works:
1
4
617
The memory system is what makes it feel most fluid and magical.. Heavily inspired by openclaw then hermes. (best part of building an agent yourself is you can pick the best parts of different systems) Semantic memory: stable facts about my work (preferences, integrations, who clients are). Always loaded. Episodic memory: daily logs of what happened. Decisions, tasks completed, context shared. Cross-session recall: a searchable index over every prior conversation. When I say "earlier we discussed X," Juno actually finds it. Thus, Juno never starts cold. It gets more knowledgeable about my work every week without me re-explaining anything.
1
154
Juno started a few months ago as three cron jobs and a half-broken Slack bot. Now it runs my consulting practice and my family life. If you've been thinking about setting your own, just start. Hermes, openclaw, whatever.. First few weeks might be rough but it compunds... Juno fits my workflow like a custom suit and it's a massive productivity unlock. Go build one if you haven't!
1
131
Been working on personal a project called drawer.so and excited to share. It's the easy way to save, share, and publish html artifacts to a domain that is yours. No hosting or deployment hassel required. You get a dedicated subdomain like.. [your-name].drawer.so... You pick :) Just connect claude, chatgpt, or your agent and start publishing artifacts. Perfect for docs, tools, presentations, and anything you can dream of. Control visibility - private / public / pw-protected I'm super excited about the simplicity and power of pure html, css, and javascript artifacts.. I've been building so many personal tools and client proposals right within claude or via my hermes agent.
1
1
7
1,129
quick little demo
1
534
built a dither tool for a client's marketing team. every designer eventually builds one. today was my day.
2
4
493
Claude is an incredible brain and orchestrator.. it only makes sense to let it handle your asset generation
3
524
you don't realize how spoiled you are on a claude max plan until you use an api key and see the costs roll in  🥲
2
4
643
Something that's not talked about enough in AI development: 👉 Your local setup and deployment pipeline. When I used no-code tools, I never thought about any of this. Dev and prod were just two modes. Build in dev. Hit deploy. Everything syncs. When I started building with code, I needed the same thing.. A playground and a production environment (at least) I quickly realized that now I was in charge of keeping them in sync. I literally tracked database changes in Apple Notes in the beginning like a madman. Copy. Paste. Deploy. Pray. It worked until it didn't. Forget one change and suddenly I'm up all night pulling out my hair. Now I work entirely on my machine with local database, test data, auth, ngrok, etc (traditional devs are rolling their eyes at this point). When I make a schema change, I run one command. It generates a migration file. Timestamped. Versioned. Tracked in Git. When I'm ready to ship I push to GitHub and the pipeline runs. Local becomes live ✨ No touching production directly and no praying (ehh well maybe a little 🙏) All that said..I'm pulling together a simple local to prod starter repo based on my current dev workflow.. It contains -- Local Supabase so you're not testing against real users. -- Ngrok so you can test webhooks and integrations without deploying. -- GitHub Actions so one push runs db changes and deploys automatically. And because I can't help myself... a component + style guide foundation. This is the setup I wish I had when I started that would have saved me some long nights... If you interested in this let me know and I'll send it your way
9
7
1,102
To whom it may concern... 10 years of product design. 18 months of shipping with AI. I'm starting to share what I've learned. Breakdowns. Templates. Guides. If that's your thing take a look here basislab.substack.com
1
2
384