Adam Argyle

Wild how far you can push "customizable select" with just #CSS

I can feel Claude laughing at the JS date code I wrote ~5 years ago, it's like "lemme refactor that (crap) for you"

Where can I read about self healing and self improvement agentic loop techniques?

#CSS spec compliant HDR Color Picker now available as a Figma Plugin nerdy.dev/css-color-pick…

the web has been quiet for a while. for the past few months i've been building something to fix that. declarative audio for the web. describe a sound as plain data, play it with one call. → audio.raphaelsalaja.com

so many thoughts lol, sup Dima 🤘🏻 there's a conflict of spectrums happening in scenarios like this, sometimes it's the CSS classes, sometimes it's the colors, sometimes it's the users browser that day, or it's the high expectations because the rest of your UI is so good they're sad an edge case is occurring. all in all, quality is worth chasing, and our quest is to make it look like it was easy, even though we all know it's not. that's the pro move. the matrix of state we balance to deliver quality ui and experiences is immense, more context than LLMs are able to hold right now, and that means sweating all the little details, all the little integrations, and buttoning up everything so your merchants or users dont have to. now i'm done writing this, i'm unsure if i answered the question lol

@soulchildpls @benjaminsehl lmao. clearly a css issue. i wonder @argyleink the CSS god in my eyes thinks about these types of edge cases with apps and theme css conflicts

Once your app gets enough merchants, the challenge will shift to supporting different theme quirks, and to work / fight with other apps (to achieve the output render your merchant wants)

This @syntaxfm jacket is rad 🤘 I don’t look as cool as @mhartington did at React Miami tho 🌴 How do I order another A so MAD backwards says ADAM?

From Emo to Ecommerce x.com/i/broadcasts/1…

Warp is now open-source.

@tomjohndesign generative ui for sure

is diffusion the next UI framework?

Current status 👀👀

Got to talk at @aiDotEngineer conf last week about the need for collaborative AI engineering. All our current coding agents are single player. We're trying to scale up individual productivity, but creating tons of alignment problems in the process. We have no good tools for...

finally sat down with claude design and it's pretty fuckin good i'm building out a static site and agent rig for some gym homies that run a local service business and this is just about perfect

New #CSS recently in all browsers nerdy.dev/CSS-recently-i…

Tons of folks are piling in here saying that AFK agents are a myth. I have been using them to ship these GitHub repos: mattpocock/evalite mattpocock/sandcastle mattpocock/software-factory (might be public by the time you see this) Here are a few steps to making this work, and some reality checks. Definitions Let's split this into the day shift and the night shift. Day shift is planning/review/QA, night shift is AFK implementation. Day Shift (part 1) 1. Use /grill-me to align with the AI 2. Use /to-prd and /to-issues to create a PRD (the destination) and implementation steps as separate tickets, which can be grabbed in parallel (the journey) 3. The PRD is a ticket, but it's not an actionable step. You just put the user stories there This is pure requirements gathering shit, same as it ever was. Night Shift 1. I run a planner agent which looks at all the tickets and sees what can be worked on now, and what's blocked 2. The planner agent then kicks off multiple agents (sandboxed using Sandcastle, my OSS tool) to implement the code 3. I then have an automated reviewer agent look at the commits produced - one agent per implementation. This checks alignment to the original PRD, as well as code quality 4. These commits end up on branches that get PR'd to main 5. The planner agent runs again until all work has been completed The review is a crucial step - it's saved me MANY times. I am planning to massively increase the amount of review I do, hopefully with multiple agents. But guess what - AFK agents sometimes produce bad code. This can happen because of: a. The original plan was bad because the best solution was something different b. The original plan was bad because it didn't take into account all the unknown unknowns, and the AI had to make some decisions during the coding session which were bad c. The plan was good, but the AI just shat the bed (twice, once in the review stage, once during implementation) d. Your codebase is bad and the feedback loops don't tell the agent if it did a good job or not So... QA: Day Shift (part 2) 1. QA all of the branches created 2. Create follow-up issues, potentially editing the original PRD to adjust the destination This will usually take a long time, often as long as planning. But then you kick off the night shift again. Once QA is all done, you review the important bits of code manually, usually in PR's. There isn't anything better than the PR UI right now, so that's what we're stuck with. Wake-up Calls 1. If you let the AI run all night unbounded by planning, it's going to produce shit code 2. Mostly, my loops finish before I go to bed, it's just the night shift catching up to the day shift 3. The only reason I do AFK at all is because it allows me to automate review and totally not give a shit about latency 4. I always run night and day shift in parallel. I can't plan that far ahead (skill issue, probably). I need working code to base my plans from, so I'm aggressively QA-ing stuff that lands

@LiveLongAndCSS p.s. I’m still bitter too

@LiveLongAndCSS I did join early in openui discussions, but was very intimidated by it. And it stalled, so I checked out. Def why I’m trying to shoutout to the folks who picked up the torch and carried it across 🫶

Hella important huge web plat feature, grats to all who worked on it groups.google.com/a/chromium.org…

@pbakaus awwww fun! i do admire gradient.style 🙂

@argyleink ah! nope, that was plain ol' cursor (well, new cursor :)). Composer 2 is a very fast model, so good for a live, uncut demo like this. Opus would produce much better results though, it's a speed/quality compromise.

Design inside your codebase. Introducing Impeccable 3.0: ▸ 1 skill, self-contained, 23 commands ▸ /impeccable live: pick in-browser, get prod-grade variants, accept writes to *source* ▸ reads+writes DESIGN.md + PRODUCT.md ▸ brand & product design impeccable.style

Unpopular opinion: "AI makes everyone a developer" is true the same way "cameras makes everyone a photographer"