Got access to @elyxdesign → yet another place where agents can run. Too many agent software tools to manage, so I built an app with Elyx to bring back some clarity. I’m loving the preview so far. I’m a big paper fan, but Elyx looks promising

I have discovered $50 amazon photo frames to be the PERFECT home display screen They can be rooted, updated to run a modern browser, have WiFi and can be powered from USB 1280×800 resolution with a nice touch screen I detailed how to hack these yourself in my latest video wesbos.com/hacking-smart-pho…

after several years... i have a new portfolio 👀 prekesh.design/

Introducing Anatomy Describe a machine in one line. Claude brings it to life. - Interactive isometric wireframes you can rotate, inspect and explore - WebGL shaders for fire, water, plasma and more - Real 3D motion, with individual parts that rotate and move Install it as an agent skill. Fully open source.

Introducing Graphical. It's a simple, powerful, and fun tool to design visual languages, style components, and work with coding agents to create interfaces that look memorable and feel unique. I hope you'll check it out at graphicalui.com!

we’re polishing a new agentic experience. things are (literally) starting to glow at @elyxdesign

The thing I learned this year is that when engineers say they like working on “hard problems”, they actually don't. What they like is puzzle solving, and having a repertoire of patterns that they can pattern match onto traditionally hard problems, usually involving databases or something with scale, etc. And they know that the industry used to pay you a lot for how deep and broad this repertoire was. Unfortunately, in 2026, well, you have a cheat code machine that has infinite breadth and depth for pattern matching. So the question is, do you actually like hard problems? Because there are now hard problems that are a complection of engineering, product, society, culture, politics, and they are fairly intractable, probably unsolvable! Because if you do want to work on those actually hard problems, there is so much money that people will pay you for it. But you’ll have to face that truth about yourself first.

🚨 side project alert 🚨 Announcing Muse Gadgets, an open source ESP32 firmware and Linux sdk so that you can make hardware devices that work with Muse. Grab an API token from gadgets.muse.ai and point your favorite coding agent at the github repo to build your own peripherals for Muse.

here's an extract from a discussion i was having in the @elyxdesign's discord with a beta tester. if you've been wondering what elyx is all about, what it does, what it doesn't do, etc. then this might help you too! elyx thrives if you treat your designs a little more like code components. even more so when they share a direct relationship with their code counterparts (e.g. button.elyx vs button.tsx). building a source of truth takes a little bit of discipline. which, let's be honest, for a very long time many of us designers had very little accountability for. we'd work in our corners, name layers however we wanted, break things into pieces based mostly on what made sense visually, often without a very good understanding of how the product was actually being built in code. that was mostly fine when design and implementation were two separate worlds. someone would eventually translate one into the other. but i think that model makes less and less sense now. if design is becoming something that teammates, agents and code all need to understand and operate on, then the structure itself starts to matter a lot more. names matter. boundaries matter. files matter. the relationship between a component in design and a component in code matters. that's a big part of why elyx can sometimes feel a bit more like an ide than a traditional design tool. it's not really trying to make the canvas less free (you can still throw whatever you want in there) but the surrounding structure is nudging you toward making things legible beyond just the canvas itself. the question for us becomes less, "how do we get you to design more before coding?" and more, "how can elyx stay useful while design and code keep feeding into each other?" that's probably the part i'm personally most excited about. not treating elyx as the place where design happens before development, but as something that can live alongside the project while it gets built.

For years, maybe a decade, I've wanted to build a writing tool that just did a few things I couldn't find anywhere else. A system that mimicked how I think when I write. A system that provided clear affordances, features, and places to do the things I wanted to do. A way to play with my writing as I'm writing it. A way to settle into just the right way to say something. It never made sense to make it a 37signals product because it's not commercially viable, nor would it be worth pulling people off their other work to hack on this. Plus, it would have taken months the old way. So this weekend I just made it myself, with Claude's help. It's called Write_On and the short video walks you through it. Essentially it's "alternative control" at the word, sentence, and paragraph level, plus a way to dim stuff back, and stash stuff near by. Not version control, but alternative control. You'll see what I mean when you watch the video below. So here it is. Write_On.

it's crazy how far out the labs are building at the application layer on the one hand it makes sense, on the other hand do you really want all of your company knowledge, docs, workflows built so locked in to a single model?