@mattpocockuk I have a skill for this and I expect to never look at a merge conflict again. It's great as a skill since it kicks in anytime the agent sees conflicts without me explicitly asking for it.
@kentcdodds I use skills at the global level more than project level. I have things like spec, plan, execute, PR, and code review installed globally so I can refer to them anywhere I am working and only have to update them in one place
@kentcdodds Are you planning to go into product marketing? I'm interested in your take on creating awareness, organic discovery, and when/where to spend money. I think it ties back to knowing what to build and can be used as a forcing function for discovery
Lots of great takes in Kent's video that will hold true over time. I especially agree with the emphasis on ownership and accountability driving you toward building the right thing. Code is cheap but your time and attention are not.
I had some aspects of this in my /project-spec skill already and it's now more explicit.
- How do we measure success?
- What are the downstream effects?
- Why should we _not_ do this?
https://t.co/MCeYHd2nwf
I just used this to map out all the code paths that would need updating to introduce an AbortSignal into a library entrypoint. So intuitive to review and execute. Thanks again @dillon_mulroy
my "plans" largely look like pseudo code composed of mostly types/interfaces, how they compose, and their boundaries
ive recently started including call stacks - been very helpful for both me and agents when implementing
I'll be speaking at Carolina Code Conference this year in Greenville, SC! Let's talk about microVMs, unikernels, and the future of cloud infrastructure