Felipe Valencia

@brian_lovin Not sure if it may be useful... But I believe it would be cool to be able to sync my GitHub stars (I use them as bookmarks, too) Just migrated all my links from Reader/Readwise to Shiori and love it.

Shiori to the rescue

@RhysSullivan Not sure... Been having a tough time with it. Dunno if skill issue lol

i dunno what everyone is on about with 4.7 it feels the same as 4.5 / 4.6, it's not exactly doing worse work it's maybe slightly better but thats it

Damn, I'm so happy with plannotator.ai. It feels like I found gold 🔥

@dillon_mulroy @ryanvogel sus....

updated setup

@RhysSullivan @DrizzleORM LMAO 😂

@DrizzleORM i have questions

@nummanali My sweet spot is 200k; going beyond that gets a bit weird.

I recommend 300k And even then, depending on the problem keep it below 150k for most intelligence Use compaction, restore with summary and guided sub agent usage

@dillon_mulroy @mjackson @badlogicgames Damn, didn't know about plannotator.ai; It was an instant install tbh. Ngl found some good resources through your posts lol.

hahah that was in jest at mario - he's definitely the brain child of it and it's so good. we used a very similar idea in our Think stuff we shipped today that was inspired by him/pi as far as my workflow goes - if i know exactly what i want and need to build i use what i guess is called "socratic method" for building up the agents initial context - basically asking it questions i know the answers to (e.g. how does x api work in y library, how is it implemented. what are the existing patterns for doing z in this codebase) so it build up its understanding. if the topics are kinda deep dives/longer thread i rewind with /tree picking out the import things it discovered. i'll continue that process for what i want to build e.g. "how would you implement a feature that x,y,z in this code, how would manage this constraint, and that edge case" at this point once it's speculated/"planned" an implementation I fire up plannator (plannotator.ai) and iterate back and forth using /plannotator-last (e.g. review and annotate the agents last message which coincidentally is kind of like a plan at this point) once i'm happy with it's understanding and approach i /tree back with the clear summary of how to implement and let it rip (sometimes i'll use @mattpocockuk's tdd skill here) once it's done its initial implementation i /tree back to the the clear summary of how to implement and then use /plannotator-review and iterate using that until i'm happy with it

i have a > 500 message single pi session that i've been working in/on for several days and haven't needed to compact once

@amorriscode @oskargroth Actually, I noticed when referencing files through @ it duplicates the items. Would be cool to have support for ctrl + p and ctrl + n when navigating the options

@oskargroth let us know if you have any feedback!

Next-gen IDE right here

@Shpigford Looks great, Josh! I'll try it this week. Also, I wonder how difficult it would be to have support for vim motions? (May explore it through a fork)

just rolled out v2 of clearly.md! kinda unreal number of updates but the tl;dr is that it's my first step towards making it a proper "knowledge base" for you and your AI agents (not just a markdown viewer).

Do things quickly --- That thing that you're convinced will take 6 months? DOA. Instead, make a plan that ships most of it in 6 weeks. You'll get the buy-in for 6 months if it's worth it. 6 weeks to delivery? Break it down into 6 1-week sprints. Setup a quick review every Monday. A 1 week sprint? Ok we can't do meetings to decide every detail, so quickly sketch out what you're doing that week, and get to work. Day 1 of the sprint? Ok, let's hack something that just works for the day. So you can show something shitty by the end of the day. Suddenly, there's no sprint culture. You just do things everyday. You get effectively infinite course correction. Things that aren't important just get cancelled. You get to show incremental progress on a daily basis. There's no time for politicking, you only want to ship. You get the joy of infinite dopamine hits. You get a reputation as the demo god, always ready to show what's changed. There's no stress of hitting arbitrary long term deadlines, the only thing that matters is what's happened. Prioritising becomes your mantra. Sorry, we're not doing a rewrite because twitter said it's cool. We only want to move forward. You're done by 5pm every day because that's what you've planned for. If it didn't happen then you planned badly for the week; correct assumptions and move forward. Everyone's on your side because you've reduced risk. Who gives af about jira/linear/github? There's code, and there's not code. You make a text file on your dekstop with "things to do" and "things done". You're done when there's nothing left in "things to do". Just do it, dammit.

@JoannaStern Mimestream and Simplify Gmail are the best ones I have tried.

Is there a great Mac email client? Like an actual great one where I won't find myself going back to Gmail web four days later.

@stylesshDev Ok bro, enough, publish it!! Every time I see a new video, it's like, I need it lol

pushing the load times to the extreme

I’m ready 🔥

@evanyou Been having similar issues. It is like a roulette; I have to start a new session and cross my fingers that it’ll be better.

Honestly don't know what happened to Claude Code. Tried a one-off simple task on a fresh directory yesterday, tried a bunch of things that didn't work, asked for a ton of permissions, and then got stuck for 4 minutes before I got tired of waiting and killed the session. This was on medium effort. Switched to Codex gpt 5.4 with medium effort and one shotted the task in under 1 minute.

@cassidoo 🔥 looks great

Have you seen the new /pulls view on GitHub, yet? If you opt in to the new experience, your pull requests get WAY more organized, with everything from custom views to collapsible sections to filtering by org and repo.

@saltyAom Helium is really simple, with nice features. Really happy with it.

Ok real question, Helium or Brave

The most frustrating part... This is when I know I may need to start a new session 😂

@tannerlinsley @clerk @ReactMiamiConf @tan_stack See you there!!

Thanks to @clerk, I too will be at @ReactMiamiConf chatting all things @Tan_Stack, Web and AI! I'm not speaking on stage this time but will be dedicating 100% of my time to the hallway track. Okay, I might watch Kent's talk, but other than that... HALLWAYALLWAYS

@fernandorojo @v0 So far, so good. Just got a team plan. We managed to redesign an entire dashboard, and v0 played a big role in helping us iterate quickly. Really happy with the platform.

@felipevalr @v0 Glad to hear it. Let me know if you have any feedback for us

Honestly, @v0 has improved a lot. I've been experimenting with it over the past few days and have come up with some good ideas; I've already made updates to a few projects.