Finding signal on Twitter is more difficult than it used to be. We curate the best tweets on topics like AI, startups, and product development every weekday so you can focus on what matters.
I share extremely practical AI tutorials and interviews | Join 140K+ readers at creatoreconomy.so | Product at Roblox
Page 1 β’ Showing 20 tweets
Most companies think being "AI agent-first" means building an MCP server. But the MCP should come last, not first. Here are 5 steps worth thinking about: 1. Don't force people to use your website/app. AI agents will interact with many products first. If your product only works when a human visits your site, you're already behind. 2. Every capability needs a corresponding API. You'd be surprised how many products have beautiful UIs sitting on top of incomplete or undocumented APIs. 3. Build single-purpose, composable endpoints. Agents want to chain atomic APIs together to achieve outcomes. They don't want a monolithic endpoint that does five things. 4. Make your content agent-readable. Your docs and help centers will be consumed by agents more than humans. Clean markdown and consistent headers are a must. 5. Build an MCP server. Note how this step comes last. An MCP on top of broken APIs or poor docs is useless. Get the foundation right first. π More on how to build your products for AI agents first here: https://creatoreconomy.so/p/why-you-needβ¦

How do I think about what to use OpenClaw for vs Claude Code / Codex? OpenClaw seems better for personal OS (because itβs mobile first) while Claude Code / Codex is better for building?
Claude Code creating YouTube Music playlists for me now based on my tastes. Any crazy stuff I dream up it seems like it can do.


I believe that: 1. AI agents will soon be the first to interact with many products 2. You should be able to use any AI model you want to build great games Our Studio MCP Server now lets AI agents iteratively plan, write, test, and modify your game. And you can now bring your own API key from Anthropic, OpenAI, or Google Gemini to build. π Learn more here: https://devforum.roblox.com/t/studio-mcpβ¦
It's funny to see all the companies with the best UI build MCP servers first - Mercury, Linear, Figma, etc. What we all need in life is WORKDAY MCP
Right now we have APIs, skills, and MCPs for your AI agent to talk to different products. What happens when your AI agent is trying to talk to another AI agent? Does it just become a natural language debate or something? π
The words "Agency" and "Taste" are all the rage these days so let me try to define them: Agency This one is easy. To me, it's simply going from: "I don't know how to do this." to "I don't know how to do this but let me ask AI and just figure it out." Taste There are no magical frameworks and you aren't born with this. I think there are a few key ingredients though to build taste. You have to: 1. Talk to users 2. Be the user 3. Listen, seek the truth, and admit when you're wrong 4. Iterate and build rapid feedback loops 5. Make time to tinker and play and most importantly... 6. Actually give a damn about what you're building and ship only something that you want to put your signature on vs. pumping out slop What are your definitions?
This is probably the most insanely cool AI product I've tried in recent memory. A swarm of AI agents designing a website from scratch. And you can edit things manually at any time (see my manual edit at the end π ).
Confused by APIs, Skills, and MCPs? Think of them like a professional kitchen. 1. APIs are the kitchen tools. Each one does a specific job. For example, Slack has APIs for sending messages and listing channels. Without tools, there's nothing for agents to work with. 2. Skills are the recipes. Text files loaded into the AI's context that tell it exactly what to do and how. "When the user asks to post in Slack, call chat.postMessage with the channel and message text." 3. MCPs are the full kitchen. They bundle the APIs, auth, and tool definitions so that the AI knows exactly what it can call and how. I believe that AI agents will soon interact with most products before humans do, so I wrote a new deep dive on how to use APIs, skills, and MCPs to make your product agent-ready. π Subscribe to get it in your inbox tmr: https://creatoreconomy.so

1. We are still incredibly early 2. Most white collar workers have no idea whatβs coming

Love getting comments like this. When there's so much hype in the AI space, just cutting out the BS is the differentiator. You can watch my no-BS OpenClaw tutorial here: https://youtu.be/ji_Sd4si7jo

We're all basically context janitors for AI at this point
Google just launched Gemini 3.1 and a new @GoogleAIStudio. I've been prototyping with AI Studio for the past 6 months and it's completely changed how I build products. Here's my new tutorial walking through what's new in AI Studio and Gemini 3.1, plus my exact 5-step prototyping process. π Watch now: https://youtu.be/2sLO9NYr8Rc
youtube.com
- YouTube
You can now prototype a new product faster than: β Writing a spec β Creating a design β Making a slide deck I made a new tutorial walking through exactly how I prototype new features in 5 steps (and validate demand with real users) using @GoogleAIStudio. π Subscribe to get it this week: https://youtube.com/@peteryangyt?sub_conβ¦ P.S. Google is cooking something good, more on that soon. π

Here's my new deep dive on why you need to build your product for AI agents first. I spent a decade obsessing over intuitive user experiences (and I still do!). But the "user" in UX is quickly becoming an AI agent instead. For example, instead of visiting @mercury, @linear, or @meetgranola, I just text my agent: β "Add my Mercury finances to your report." β "List my Linear tickets in your briefing." β "Takeaways from my meetings today?" For many products, AI agents will be your first users, not humans. My new deep dive covers: βοΈ APIs, skills, and MCPs: a quick primer βοΈ 5 steps to build for AI agents first βοΈ What you can do this week π Read now: https://creatoreconomy.so/p/why-you-needβ¦

Why You Need to Build Your Product for AI Agents First
"I woke up and he already built a website, created a product, set up Stripe, and launched." Here's my new episode with @nateliason on how he set up his OpenClaw bot, @FelixCraftAI, to build a business that made $14,718 in 3 weeks. We talked about: β The 3-layer memory system that prevents your bot from forgetting things β How to run 5 chats with your bot at the same time β How to safely give your bot Stripe, Vercel, and X access Some quotes from Nat: "Every time Felix asks me to do something, I ask: Can I remove this bottleneck so you never have to ask me this again?" "I'm never in Claude Code or Codex myself anymore. I just tell Felix to do it." "If you get the memory system and the proactivity right, it solves 90% of the frustrations that most people run into." π Watch now: https://youtu.be/nSBKCZQkmYw Thanks to our sponsors: @linear: The AI agent platform for modern teams http://linear.app/behind-the-craft @Replit: From 0 to full stack app in 2 min. https://replit.com/?utm_source=creator&uβ¦
Your goal in the AI agent era should be to get user time spent with your product to 0 because youβve made it so incredibly easy for agents to get work done via APIs/skills/MCPs.
There seems to be two camps about OpenClaw: "OMG I have an autonomous AI agent team running on 5 Mac Minis!" "OpenClaw is all hype and BS - there's no real use case." My friend @nateliason decided to give his OpenClaw bot, @FelixCraftAI, $1,000 to build its own business 3 weeks ago. Since then, Felix has made $14,718 by launching its own website, info product, and marketplace for OpenClaw skills. Nat gave me an inside look at how he set Felix up β including his 3-layer memory system, security, and daily workflows. π Subscribe to get our full episode tmr: https://youtube.com/@peteryangyt?sub_conβ¦

How I prototype new products in 5 steps: 1. Build a base template First, I screenshot my product and ask @GoogleAIStudio: "Build this and make it interactive. Keep styling exactly the same." 2. Prototype the new feature I use a prompt to make AI my design partner and then we explore the feature idea together. Then I ask it to build. 3. Iterate with AI AI won't nail the solution in one shot. So I usually go back and forth with it a few more times until it's good enough to share. 4. Collaborate with team and real users I share the prototype with my designer, other stakeholders, and real users. They can remix it and add their own ideas. 5. Turn the prototype into a real product By this step, I've already validated the idea with real users before investing in specs, designs, and engineering. π Watch my full tutorial to see this process in action with a real example: https://youtu.be/2sLO9NYr8Rc
youtube.com
- YouTube
I've spent over a decade obsessing about building great user interfaces but have to admit the "user" part is becoming increasingly less important when agents will take a first pass at everything. Your product and platform (and even internal doc) needs to be agent optimized.