Launched this week

pudge-ui

Launched this week

A tech-stack-agnostic, UI design spec, written for agents.

8 followers

A tech-stack-agnostic, UI design spec, written for agents.

8 followers

Visit website

A design system written for coding agents, and humans. No install, no components. Just specs that your agent reads to build skeuomorphic 2000s UI (Walkman, iPod, Nikon dials) in any stack, for any platform, any technology. Ships an MCP server. 90+ components, completely open-source with MIT.

Interactive

Free

Launch tags:Design Tools•Open Source•Developer Tools

Launch Team / Built With

Viktor.comAn AI coworker that actually does the work

Promoted

Maker

📌

At Pudge Studio, we embrace the horizons that are opened by agentic programming, and we believe we as engineers need to embark on creative endeavors with these tools more than what we are doing right now. We are in the process of creating a line of products catering to artists, creatives, and developers, all co-authored by frontier models. But while designing our products we noticed how exhaustive the agentically-produced UIs have become. The same slop. Flat, purple or gray. We wanted to give our products a distinctive character. A personality our upcoming users can resonate with. A design language that speaks to your eyes, while providing a pinch of nostalgia. Our designers and engineers curated an internal design system which communicates directly to our agents, blurring the lines of tech-stack, setups, and dependencies. And now, we were just an MCP call or a single prompt away from writing depth-model, metallic finish components in whichever technology we were using. Everything from Tauri apps to native android. Over time, we polished it further, and now we are happy to announce the public release of v0.2.0 of "pudge-ui", our design system that teaches agents to make tactile, physical, 2000s-electronics interfaces. These are not just interfaces, your agent doesn't just digest how the component looks, they also digest how that physical component is supposed to function mechanically. So you are just a prompt away from adding motion, movement, haptics, and much more! The best part is the format. pudge-ui isn't a component library, it's 90+ (we will be adding more) written specs. Each one describes the real hardware it imitates, how the mechanism works, the exact CSS, and the constraints. Agents read specs better than they read token files, so the output is faithful and works in any stack (CSS, RN, SwiftUI, Compose, Flutter). Add the MCP server and just ask your agent to "build a music player with pudge-ui." It is working magic for our team, and as a very new and fresh studio, we would love your feedback on the component specs.

Report

1d ago

The skeuomorphic throwback is genuinely charming, and feeding specs to my coding agent instead of installing a heavy lib feels like the right call. Curious to see how the MCP setup holds up on bigger projects.

Report

19h ago

Maker

@yeterz1o2 Thank you, we are glad you like it.

You can try the mcp server on any new or existing codebase of any stack. While we are optimistic about its performance, we also believe that there's still a lot more work that can be done, afterall, we are still at v0.2.0

we are currently testing some beta versions on our upcoming projects, so we are hopeful :)

Report

18h ago

Love that you zeroed in on the skeuomorphic 2000s aesthetic with real specs instead of just slapping a CSS framework together, the MCP server move is really smart for letting agents actually get it.

Report

1d ago

Maker

@azatv0rh Thanks a lot. While testing the initial internal versions of the design system (we used to call it chroma-01 earlier), we started with feeding the entire component directory to the agents in form a html file. While it did get the job done, we noticed the agents struggling and hallucinating with the implementation of movements, variants and different states of the components. After a deep research on the physical aspects and mechanical structure of each of these components, we ended up at the detailed specs which did not just give the agent the interface of the component, but also its implementation, possible movements, and depth model. We are glad you like it.

Report

22h ago

Love that it leans into skeuomorphic 2000s vibes instead of yet another flat minimal look. The idea of just feeding specs to a coding agent and skipping the install step actually sounds painless to try.

Report

17h ago