We're the SERP Position number 1.
Visit ventlabs dot com dot ng
We don't understand why @X considers our link malware. Written support to understand why .ng domains are profiled so.
Figma just launched AI agents that design directly inside your canvas.
Not a concept. Not a waitlist. Open beta. this week.
This is the biggest shift for designers since components were introduced β and most people in your timeline haven't posted about it yet. That's your window.
Here's what it actually means for your workflow:
β AI agents now operate inside Figma with full design-system context β your tokens, components, and constraints. Not a plugin. Not a sidebar tool. On the canvas.
β This is built on MCP (Model Context Protocol). It crossed 97 million installs this month. Every major AI lab ships it. If you don't know what MCP is, learn it before your manager does.
β The designers who win from this aren't going to be the ones who read the most threads about it. They're going to be the ones with a real workflow demo by Monday.
My take: the skill gap is no longer "how fast are you in Figma."
It's "how well can you direct an agent that's inside Figma."
Same taste. Same eye. New lever.
Open the beta this weekend. Build something.
Be the person in the room who already knows how it feels β not the one asking what it is.
What's the first component you'd let an agent take a pass at? π
#DesignEngineering #FigmaMCP #AIDesign #UIUX #BuildingInPublic
Claude just became a desktop agent.π±π±π€―π€―
From your phone, you can now tell it to open Figma, navigate your browser, fill spreadsheets, export files, and it executes on your desktop.
This is not a concept. It shipped yesterday.
Here's what this actually means for designers:
The busywork is fully delegatable now.
πΈResizing assets, renaming layers, batch exporting, switching between apps , every low-cognition task you still do by hand. Brief it from your phone. Walk away.
The interface is no longer a click. It's a prompt.
The fastest designer in the room used to be the one who knew every Figma shortcut. That era is done. The designer who wins now is the one who can give the clearest brief to an agent.
Direction > execution.
And it's not staying in one app.
Microsoft just embedded Claude directly into M365 Copilot.
Your clients' Word docs. Their Excel sheets. Their PowerPoint decks. AI is no longer a tool you opt into β it's inside the software they already pay for.
The question isn't "should I learn this?"
It's "how long can I afford not to?"
What's the first thing you'd delegate to a desktop agent? π
#DesignEngineering #ClaudeAI #AIDesign #UIUX #BuildingInPublic
Shopify just moved checkout inside ChatGPT, Copilot, and Gemini. π€―π€―π€―
No browser visit. No storefront. No landing page. The user types, the AI replies, and the product gets bought β all inside a chat window.
This is called Agentic Storefronts. It's live today.
Here's what this means for designers:
The UI is now the conversation.
The hero section, the product grid, the sticky nav, the CTA button β none of it loads. The AI describes the product and handles the sale. The screen you designed never opens.
Design is moving up the stack.
The new design surface isn't a Figma frame. It's the product data, the brand copy, and the content architecture that the AI pulls from when it answers the customer. That's what you're designing now.
Your value just shifted to the brief.
The designer who wins in this world isn't the one who built the most beautiful storefront. It's the one who built the brand system the AI knows how to speak from. Content strategy, information architecture, brand voice β these just became core design skills.
The storefront isn't dead everywhere. But the assumption that every purchase begins with a screen you designed? That just ended.
What do you design when the interface is a chat window? π
#DesignEngineering #Shopify #AIDesign #ProductDesign #BuildingInPublic #Openclaw
Anthropic just quietly dropped a model tier above Opus. They're calling it Mythos.
No big launch event. No countdown. Just a new ceiling.
It delivers dramatic improvements in coding, academic reasoning, and cybersecurity. It's compute-heavy today β which means it's expensive, which means most people will sleep on it. That's your window.
Here's what this means for designers building on top of AI:
Every tool you already use just got an engine upgrade.
Claude Artifacts, Cowork, Figma plugins, Copilot β the model underneath your workflow gets stronger whether you asked for it or not. Your output ceiling rises automatically. The question is whether you're asking enough of it.
The gap between power users and everyone else is widening fast.
When a new frontier model drops, the people who learn to direct it well in the first few weeks compound ahead of everyone who waits for the tutorials. Mythos rewards specificity. Vague prompts get average outputs. Sharp briefs get extraordinary ones.
And OpenAI shipped the same week.
GPT-5.4 landed with native computer-use built into Codex this month. Two frontier labs. Both now with agents that operate your desktop, navigate your browser, and run your tools from a text prompt.
The chat box era of AI is over.
We're in the agent era now. And the floor just raised β again.
Which Mythos use case would you test first? π
#DesignEngineering #ClaudeAI #AIDesign #BuildingInPublic #FutureOfDesign
My buddy @uiuxbyvicko reached out to me this afternoon concerning a zero state empty state issue, so I decided to write this.
Most designers treat Empty State and Zero State as the same screen.
They're not. And that distinction is where good products separate from great ones.
Zero State = first run. The user has never added any data. This is an onboarding problem disguised as a design problem. A blank screen with "No projects yet" just abandoned a new user at the worst possible moment.
Empty State= post-action. The user cleared, filtered, or finished something. This is earned. "You're all caught up β" feels completely different to "Nothing here" β even though the UI is identical.
Same component. Opposite emotional context. Two different copy jobs.
Here's how to handle both:
β Zero State: Don't show blank space. Show possibility. Seed it with a sample project, a getting-started prompt, or a single clear CTA. The user needs a handhold, not a void.
β Empty State: Acknowledge what the user did. Inbox zero deserves a moment. A cleared task list deserves a beat. These are micro-wins. Design celebrates them or wastes them.
β One screen. Two states. Write the copy twice. Ship it right. This is what separates a product that *feels* considered from one that just *works*.
The β symbol on your screen isn't neutral. It's either an invitation or a dead end. You're the one who decides which.
Is the screen below an empty state or Zero state?
#DesignEngineering #UIUX #ProductDesign #UXWriting #BuildingInPublic*
A few weeks ago a random company emailed me if I wanted to try their foldable monitor for digital nomads
They didnβt asked for anything, just sent it for free
And itβs actually nice, laptop-sized, anti glare and usb C
But why would they do that? Itβs like $600, they didnβt even asked for a post or even review, they just sent it and asked how it was
Can we have this type of game on @ton_blockchain TON?
All I need from you is your retweet to drive this to the ends of the Blockchain.
Designed and animated by yours trulyππ»
#uidesign#gamedesign#TONCHAIN π