CodeHagen

Introduction HagenKit - the next OSS boilerplate ✨ And its free for everyone 🤯 hagenkit.com Launch your new project in 2 minutes – from clicking the button to live preview ✨ Techstack: 🌐 App: @nextjs ☁️ Hosting: @vercel 🎨 UI: @shadcn 🗂️ ORM: @prisma 🛢️ DB: @prisma ✉️ Mail: @resend 🔒 Auth: @better_auth I wanted to make it as easy that i can for you to get started with your new project. → We make the Github-repo → We make the Database → We push this to Vercel. Hope you like it ✨

@emilkowalski Did this a few weeks ago for - animations.dev Works like a charm ✨

Something I like to do recently is ask Fable to make me a skill out of someone’s publicly shared knowledge. If someone writes about say marketing for developers, I send Fable a link to their articles and tell it to make me a skill out of it. Then before sending a marketing email for example, I ask Fable to run it through that skill and show me how it can be improved. This applies to anything really, writing, designing, etc. as long as there’s some publicly available data that you think is good. So again, taste plays a role here as well.

@shadcn @devongovett Shipping king 👑

React Aria is now available in shadcn/ui. Use `--base aria` or choose React Aria in shadcn/create. All components, docs, CLI, styles and skills have been updated for React Aria Components. Shoutout to @devongovett who did most of the work behind this release.

@StianWalgermo @AppStore Lets gooo

Day 3 since submitting to @AppStore 💪🏻

@shadcn 👀

Launch day.

@elie2222 Yeah i know 😅

Yamal playing Messi in the World Cup finals is one of the craziest stories of all time. We’re living in a GPT 10 matrix.

@JayHoovy Well sir, this explains alot ✨

My CEO Coach called me out on something last week that I can't stop thinking about. We were talking about why I have 50+ ideas in my notes app and maybe 3 of them ever see the light of day. And he helped me realize something uncomfortable: I pre-extract the dopamine. I'll get this idea for a video, a campaign, a product feature, whatever. I can see the finished version so clearly in my head. How the audience will react, how it'll feel when it's done, all of it. That visualization is so vivid and so satisfying that my brain basically marks it as "complete." Then when it's time to actually sit down and do the work, reality feels like a downgrade. The lighting isn't right and the script feels off. The edit takes 4x longer than I imagined. And I lose interest. Because I already got the hit. I've been calling it the "Dopamine Execution Gap". The distance between how good something feels in your imagination vs. how tedious it feels to actually build. My guess is a lot of creative founders deal with this and don't even realize it. You're not lazy or unfocused. You might just be so good at visualizing the end state that your brain thinks you already did the work. What's been working for me: I stopped letting myself sit with an idea for more than 24 hours before I take one concrete action on it. Even if it's ugly. Even if it's a rough draft that makes me cringe. Because the cringe version that exists will always generate more results than the perfect version in your head. Anyone else deal with this??? Hopefully I'm not alone haha.

We’re open sourcing @​shadcn/helpers, a new package for small, focused utils to help you build and test components faster. Starting with `createChat` for AI SDK and TanStack AI. It lets you script a conversation between a user & assistant then run it through `useChat`. Your components receive native messages through the framework’s real streaming lifecycle. createChat supports reasoning, tool calls, data, files, sources and parts. Use it to build components, previews, scripted demos and deterministic tests.

@marclou Yes, this is amazing

my new feed is full of indie hackers i follow, it's so nice 😊

@zenorocha @resend Love it, everything should be headless. Imagine generative UI in a few years ✨

we're starting a new project internally... it's called *The Headless Dashboard Initiative* the goal is to make sure that everything you can do on the @resend dashboard, you can also do via: • API • SDK • MCP question: which endpoints should we build first?

@haydenbleasel Love it! Was starting to build something like this with Helpbase a while back. keep pushing ✨

Introducing Blume 🪷 A world-class docs framework for everything you ship. Drop Markdown into a folder and ship a full docs site with no app boilerplate. → zero-config setup → automatic SEO and AEO → 30+ components → powered by astro + vite → open source, free forever

@shadcn @TheSpacerr Love it, keep then coming 🔥

@TheSpacerr @CodeHagen Will continue working on chat interfaces for a bit. Bring all these together.

@shadcn /typeset is stupidly good. Imported one CSS file, wrapped 3 surfaces in a typeset class, done. Instant editorial typography ✅

@shadcn Lets go 🔥👌

Introducing shadcn/typeset. You know how you render markdown and get back plain, unstyled HTML? Headings, paragraphs, lists, tables. So you style the elements one by one: font sizes, line heights, spacing. You do it for your blog. Then you do it again for docs. Then again for the chat. Every time, you're fighting the same thing: sizing and spacing. To fix this, we created typeset.css: one file that styles everything inside a typeset container. It lives in your project, so you can change it directly when you need to. And we made it work beautifully with streaming markdown.

@hagaetc Yes 🔥

Haaland!!! 🐐🇳🇴🚣❤️‍🔥

@TomasJansson @shadcn It was basically for me to see the UI at first and tweak. Then i make a design.md for it so that the agent can look at after. Have so far worked like a charm ✨

@CodeHagen @shadcn Won’t the page take up a very large part of the context if you feed it to the llm? Wouldn’t it be more effective to let the AI figure out what kind of UI element it needs and then provide a way to find that element in your design system?

This made me develop MVPs x10 times faster 🤯 I create a /playbook page at the start of every project now. Just init a project from @shadcn and your ready to go This page lists all the UI components my project will use: ◆ Page shells ◆ Layout patterns ◆ Component structure ◆ Design rules Give the AI this context upfront and it stays consistent across the whole build Can basically design the full MVP in one go now.

@RhysSullivan This is good - Great job

@runsonai @herdrdev Thanks @elie2222 have been talking good about @herdrdev - Maybe i should try

@CodeHagen I recently moved to @herdrdev to have opus/fable be main orchestrator, but then it can manage claude/codex/pi all together. Then plugged my hermes with it as well to be able to continue what's going on.

What am i missing? 👀 I think my multi-agent setup works well, but maybe I'm not tokenmaxing 🤔 Running 5 AI agents in parallel right now: ◆ Fable as orchestrator ◆ Opus 4.8 / Sonnet 5 as sub-agents ◆ Each agent handles a different task Is this the right way to do multi-agent workflows or is there a better approach? What are you using?

@plainionist This was a DD-rom migration for a M&A product. Did i use to much? 😅

@CodeHagen What was the task that you need that much AI power?

@noahlh Thanks for the tip - Then i keep going with ✨

You’ve got it right. This is the current meta. The only thing I’m still torn over is whether Opus or Codex 5.5 is better at implementation. I think it’s task-dependent - anything visual/design related goes to Opus, anything mechanical goes to Codex. I honestly wish we didn’t have to think about this and could just use Fable for everything, but such is life with a budget.

@TJae @shadcn Gonna do it, just need to make the repo ✨

@CodeHagen @shadcn Open source it if you’re the man!