Lokuma Design Agent, is an AI designer your agents can call, a design intelligence layer for agents like OpenClaw, Claude Code, or Codex. AI can generate almost anything. But generation isn’t design. Turning raw outputs into something clear, structured, and visually refined still requires design thinking. Built by design tool makers, Lokuma helps AI reason about layout, typography, and visual balance — transforming outputs into landing pages, websites, and campaign pages that feel designed.
Before this, I built Readdy and Creatie — tools used by over 500,000 designers and creators. Most of my work has been around design systems and how products actually feel, not just how they function.
This time, I’m working with a small indie team — a mix of designers, AI researchers, and people from growth and marketing.
Recently, something started to shift.
Tools like Claude Code, Cursor, Codex, and even things like Google Stitch, are changing how software gets built.
We’re no longer just using tools ourselves.
We’re starting to work with AI, and AI is starting to use tools on our behalf.
That changes the interface.
The new “user” of many tools is no longer a human - it’s an agent.
And most tools today aren’t built for that.
AI can generate almost anything. But generation isn’t design.
What we see today, including a lot of outputs from varied AI agents, is that AI can produce UI, code, layouts very quickly. But the results often lack structure, hierarchy, and visual coherence.
They work. But they don’t feel designed.
That gap becomes much more obvious when AI is the one building.
So we started thinking:
If agents are going to build products, they need something closer to a designer, instead of just another generator.
That’s why we built Lokuma Design Agent.
It’s a design intelligence layer for AI - something your agents can call to reason about layout, typography, hierarchy, and visual balance.
Your AI handles logic and generation. Lokuma handles how it actually comes together.
Why now?
Because we’re entering an agent-first stack. Coding has agents. Research has agents. Execution has agents.
Design is still missing.
Why us?
Because our team brings together experience across design tools, real product building, AI systems, and growth.
We’ve spent years understanding what makes interfaces actually feel right, and now we’re translating that into something AI can use.
We’re still early, just a small indie team moving fast. But this feels like a new category: tools built not for humans, but for AI.
Curious how others here see it:
If your AI is already writing code, what’s still missing for it to ship something that feels complete?
This looks like a design tool. But it's actually solving a coordination problem.
Right now, the bottleneck in AI agent development isn't intelligence — it's presentation. Agents can think, but they can't express themselves visually without a human designer in the loop.
What you're really building is the translation layer between what an agent can do and what a user is willing to trust.
Because here's the part nobody talks about: users don't trust capability. They trust experience. And experience is design. The agents that feel trustworthy will outperform the ones that are technically superior. Design isn't the skin. It's the bridge between intelligence and adoption.
This is really interesting and would love to use it for our frontend team! Curious if users are vibe coding on other web platforms like Replit, how they'd integrate this?
The "generation isn't design" framing cuts most AI tool builders quietly avoid.. Curious whether Lokuma reasons about RTL layout nd Arabic typography because that's (in my pov) where most design AI completely falls apart in MENA markets. Congrats on the launch!
Congratulations on the launch! Another great tool in the OpenClaw ecosystem.
curious how it handles design consistency across different outputs, does that work or is every output basically a fresh start?
congrats on the launch @mu_li and nice thought of adding design intelligence to AI agents instead of hoping code‑first tools magically produce good UI.
But how do you keep the output visually consistent without killing the agent’s creative freedom ?
@mu_li How does Lokuma handle the balance between maintaining a strict design system and allowing for the creative 'improvisation' needed for unique marketing pages?
I feel I’m in the wrong place. The design we are talking about here doesn’t seem to be graphic design😂
Well done @mu_li !! It moves fast without sacrificing craft.
Most AI outputs feel like rough drafts. Lokuma feels closer to something you’d actually ship. The structure, spacing, and visual decisions make a real difference.
Very Very cool! let me try it today! I really need a designer to uplift my sites right now :P
I’ve seen Mu work on design-heavy products before, so this direction makes a lot of sense to me.
Congratulations on the launch! We work in the same industry and fully understand the need to use AI agents in the right way.
Can I create an agent for the whole team of 20+ designers to manage the progress and share feedback?
Super interesting! I’m going to check this out!
Congrats on the launch!
Finally, a designer for my agents! I use OpenClaw and Codex daily, and having a way for them to actually reason about hierarchy and balance instead of just spitting out generic components is a game changer. Huge congrats to the team for identifying this missing piece!
Yesterday, Google launched stitch 2.0 which has already got most of capabilities. How do you differentiate your USP now?
Rohan Chaubey
Hi Product Hunt,
I’m Mu, founder of Lokuma.
Before this, I built Readdy and Creatie — tools used by over 500,000 designers and creators. Most of my work has been around design systems and how products actually feel, not just how they function.
This time, I’m working with a small indie team — a mix of designers, AI researchers, and people from growth and marketing.
Recently, something started to shift.
Tools like Claude Code, Cursor, Codex, and even things like Google Stitch, are changing how software gets built.
We’re no longer just using tools ourselves.
We’re starting to work with AI, and AI is starting to use tools on our behalf.
That changes the interface.
The new “user” of many tools is no longer a human - it’s an agent.
And most tools today aren’t built for that.
AI can generate almost anything.
But generation isn’t design.
What we see today, including a lot of outputs from varied AI agents, is that AI can produce UI, code, layouts very quickly.
But the results often lack structure, hierarchy, and visual coherence.
They work.
But they don’t feel designed.
That gap becomes much more obvious when AI is the one building.
So we started thinking:
If agents are going to build products,
they need something closer to a designer, instead of just another generator.
That’s why we built Lokuma Design Agent.
It’s a design intelligence layer for AI - something your agents can call to reason about layout, typography, hierarchy, and visual balance.
Your AI handles logic and generation.
Lokuma handles how it actually comes together.
Why now?
Because we’re entering an agent-first stack.
Coding has agents. Research has agents. Execution has agents.
Design is still missing.
Why us?
Because our team brings together experience across design tools, real product building, AI systems, and growth.
We’ve spent years understanding what makes interfaces actually feel right, and now we’re translating that into something AI can use.
We’re still early, just a small indie team moving fast. But this feels like a new category:
tools built not for humans, but for AI.
Curious how others here see it:
If your AI is already writing code,
what’s still missing for it to ship something that feels complete?
— Mu