3 ms·
I see what this is going for but can’t help but feel like it’s overwrought. It feels a bit like the most likely outcomes are increased token burn, review surfac
by appplication 2mo ago
I see what this is going for but can’t help but feel like it’s overwrought. It feels a bit like the most likely outcomes are increased token burn, review surface, and time per task vs not using this.
Who knows, maybe that’s a good thing.
- jlund-molfese 2mo agoI feel that way about a lot of very long instructions. It seems that many of these projects are not benchmarked, so it's difficult to know whether there is an improvement in any circumstance, and what the cost is. Of course, a benchmark will be fuzzy, because codebases are all different, but it'd be a start.
- mhitza 2mo agoRelinking the recent study which argues that many instructions in the context are not followed through https://news.ycombinator.com/item?id=49096969 https://news.ycombinator.com/item?id=49096969 Many of these skills, rules, "playbooks", and such are kitchensink attempts at steering the model. It augments the model to frame it's reasoning according to project rules and flows, but cannot be really trusted to adhere to it. More of a vibe guideline.
- imadierich 2mo ago[dead]
- kanfilior 2mo agosee the team-boot skill, it is lean