I promised a funny story. I was so excited about the requirements that I took the laptop to bed just to get a few more tasks spec'd before I went to sleep. I did the specs and got a loop going. My tired brain instantly gave me the reward and I went to sleep. Laptop unplugged.

haha we need a portrait 8k screen to fit all that 😆

yeah man go try it, it's fire 🔥

thank you 🙏 I will be writing more about setup and best practices, want to get enough experience with it so I don't put some crap out there haha

I've been having these thoughts popping in for a while now, had to put some meat on them. It's good to take a step back and think about our roles as developers in the past, now, and in the future :)

bootstrap with a CLI or boilerplate

haha I zoomed in too. There's a really long scroll in there I couldn't fit most of the doc 🤣

if you notice it right away, stop the loop and undo commit/changes and then improve the spec for the feature and/or validation criteria If it's something it did hours ago, add another spec describing a fix so it will pick it up in a future iteration

the 2% learn the basics now so they can use this tool to their advantage I'm not claiming it's magic, I'm trying to say we should learn this to evolve AND IF you do at this point in time you'll have a good lead on everybody else

check :) They are essentially the perfect mix between rules and commands. Don't use up the context but can be very detailed

Yes sir, I will share every single detail. I am not 100% happy with the setup and don't want to put out a half-baked approach. Even though I make good progress on a few projects, I am finding issues daily and tweaking the setup. Will share once I am more happy with it 🙇‍♂️

Will share the entire setup, please stand by

my 3d workspace in the browser :D Use react-three-fiber and r3f fundamentals skills with a copy of their examples in the repo. It's incredible and addictive.

I'd be super interested in that too yeah! if only there were 36h in a day :D

Yes DOCKER_DEFAULT_PLATFORM=linux/amd64 docker sandbox run claude --model opus --permission-mode acceptEdits -p "..." I have it set to x86 so Playwright can run in there on MacOS

I mean the loop itself is, but there are some fundamentals around it that move the needle IMO

init from a CLI or boilerplate and install some of the man libs you plan to use and config them. For example install playwright and configure it before it can waste a ton of time setting up basic things in a bad way