Design engineer friends, I made a new thing to make your life easier. Releasing Liquid Layout, a small, powerful, familiar and extensible layout engine for the web, inspired by SwiftUI's engine. It's an excellent choice when you need to do layout where CSS doesn't help you, like the Canvas. It is powerful out of the box, and can be integrated anywhere. Build a layout tree, then query the calculated positions and dimensions on the nodes. - Zero dependencies, 4.5 KiB - Beautiful API - Fast - Extensible: write your own layout nodes and use them together with the builtin ones! - Batteries included: VStack, HStack, Padding, etc... The layout in the below @threejs demo is driven entirely with Liquid Layout. Also, I heard ya'll like Lissajous curves. :)

Excited to share our most powerful new Claude Code feature: dynamic workflows! Mention "workflow" in a prompt and Claude will dynamically create an orchestration plan that it strictly follows, allowing you to confidently trust that every stage happens in the right order even across 100s of agents.

llms should really learn to copy code with tool instead of using tokens it's insane

go check "Allow access to file URLs" in the extension settings. I'll update docs tomorrow.

Yesterday I demo'd how copy pasting marketing images from @usenotra to Figma would look like Today we added @paper support which has been a breeze thanks to @stephenhaney Soon you will be able to generate images using Notra and paste them directly in your favorite design tool!

Dear frontend devs and UI designers. I bring you Liquid DOM, a complete and faithful implementation of Liquid Glass on the Web. - Shape morphing - All properties animatable - Dynamic refraction and reflection - Adaptive tint - Adaptive specular highlight - Dispersion - Full html integration - Super fast layout engine that works across Canvas and html - Pointer event handling - Framework and renderer-agnostic low level API - High level React API - Ootb @threejs and r3f integration And lots more. Read on for implementation details and demos.

big 1. conceptually this removes a lot of questions around preview environments, staging urls, testing with "real" data, version skew, etc. you gotta be a little careful with database schemas and migrations, but you should already be doing that tbh.