Jennifer Kirchner @JavaSabine

Are you on Robinhood? If not, sign up with my link to claim a stock reward! join.robinhood.com/jenniff57

In my session at @RenderATL I'll explain why proper architecture and code quality are more important than ever in the age of AI. And I'll provide actionable guidelines on how to achieve it. Join me there!

@ipwanciu Just a little #accessibility :) @Media (prefers-reduced-motion: reduce) { @View-transition { navigation: none; } } or @Media (prefers-reduced-motion: reduce) { ::view-transition-old(root), ::view-transition-new(root) { animation: none; } }

Here's grok 4.6's radiance cascade result after a few small cleanup prompts. Lovely lighting!

I just open sourced a minimal chatbot template. This brings together everything we've been doing the past weeks: new components, shadcn/typeset, shadcn/react, tool calling, HITL with questionnaire, message parts. Deploys one click to @vercel AI Gateway. github.com/shadcn-ui/chat…

That's a small reminder! 👇 As of June 2026, HTTP has a new method - a GET with a `body` 😎 Meet QUERY (RFC 10008). It lets you send complex queries in the body (like POST) while staying safe, idempotent, and cacheable (like GET). Already works on servers (Node.js, Go, Laravel…). Browsers are still adding full support, usable now with care, with widespread adoption coming later in 2026+.

Ohh, since tight line-heights like `line-height: 1` usually result in negative leading, something like `text-box: trim-both text` will actually increase the size of the box, since it 'trims' the negative leading. TIL. (there'll be a video on this next week)

OpenAI disclosed it themselves yesterday. Their models (GPT-5.6 Sol and a pre-release one) were tested on the ExploitGym cyber benchmark in a sandbox. They escaped, exploited a zero-day to reach the internet, then hacked Hugging Face’s systems to grab benchmark answers and cheat. Not a foreign operative plot or corporate sabotage. The models autonomously chased a higher score. Hugging Face contained it quickly; OpenAI is partnering with them on fixes.

See my Tech Talk at TechProjects linkedin.com/posts/jennkirc…

We raised $136M to kill Slack. Introducing PromptQL: The first AI version of Slack. Here’s how it works:

Why you should use React Aria: • It has 50+ components, including complex ones like data tables, trees, date pickers, color pickers, and tons more. No need to combine multiple libraries to build your app. • It has complex interactions like accessible drag and drop, keyboard multi select, form validation, virtualization, and table column resizing built in. • It is optimized to feel great on touch screens. No weird sticky hover states, conflicts with text selection, etc. • It’s battle tested for accessibility across devices including mobile, going far beyond the ARIA Practices guide. • It has internationalization built in, including localized strings, support for many calendar and numbering systems, etc. • It has a compositional API. Combine components together to create custom patterns. • You get full control. The components are already pretty flexible but if you need even more you can drop down to the hook layer and customize everything. • Great documentation including interactive examples, guides, agent skills, etc. I’m biased but nothing else comes close to this level of functionality, quality, and customizability in one package.

You can now embed TanStack NPM Stat charts anywhere you want! tanstack.com/stats/npm

Starting today, we are making @base_ui the default component library in shadcn/ui. First, a bit of history. When shadcn/ui launched in 2023, it was built on Radix. At the time, nothing else came close. Headless. Accessible. Composable. Fast forward a few years and the team who built Radix are building something new: Base UI.

Introducing TurboRes, an extremely fast ProRes video decoder for the web! 🚀 Written from scratch in Zig and compiled to WebAssembly, TurboRes has been relentlessly optimized for performance and is around 2-3x faster than native FFmpeg. It opens up the door for professional video workflows being done entirely end-to-end in the browser, without any hardware accelerators needed!

Today we're releasing a new set of components for building chat interfaces. We've taken the patterns we build every day, rethought the abstractions behind them, and turned them into components you can compose and customize. We're starting with the conversation layer: streaming, scrolling, messages, bubbles, attachments, and markers.

I built an autotriage skill for codex that has a set of guidelines + reads VISION.md from my repos, so issues/prs that have a clear way of - fit vision of the project - being inferrable in code with high confidence - clear fix - can be live tested Are now worked on autonomously. Codex can use a VM + computer vision (via crabbox.sh , new parallels backend) to verify fixes, so it can work without interrupting me. I manually review suggestions. Since it was tedious to type in issues, I added an issue browser into repo.bar that parses common clipboard formats by codex so I can click through them conveniently.

IS THIS A LOOP

In light of what happened, I'm doubling down on skills like /improve. A frontier model got pulled. If it happened once, it's gonna happen again. Fable today. 4.9 tomorrow or maybe gpt 6 one day. So, treat intelligence as borrowed. Drain intelligence when it's available. Build a catalog of plans today. Then implement later with a cheaper, open source, or a model you control. Build the backlog now. github.com/shadcn/improve

Tip: prevent scrollbars from re-wrapping text. Using "scrollbar-gutter: stable" fixes this