Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agent skills that bring team coding standards to Claude Code and Codex

github.com

Post reply on HN
Print view View original

1–10 of 52 posts

Re: Agent skills that bring team coding standards to Claude Code and Codex

#3

Post by appplication »

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.

Re: Agent skills that bring team coding standards to Claude Code and Codex

#4

Post by Stitch4223 »

The promise is nice, yet I find the readme very hard to understand. So I’m not sure how it solves these problems exactly.

First off I would expect a (team) methodology to be referenced. There are tons to choose from. From that point on other terms may make more sense.

For example:

“ Pillar 2: Product Strategy & Architectural Governance (PDRs & ADRs)

Factor III — Mission Definition. Factor IV — Structured Planning. Factor IX — Traceability.”

Why are the Roman numerals in that order, what do they reference and why. Why is this Pilar 2. Etc. It’s easy to get lost in this, even if it would be the best approach in the world.

Re: Agent skills that bring team coding standards to Claude Code and Codex

#5

Post by jlund-molfese »

appplication wrote: post #3

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.

I 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.

Re: Agent skills that bring team coding standards to Claude Code and Codex

#7

Post by imadierich »

appplication wrote: post #3

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.

[dead]

Re: Agent skills that bring team coding standards to Claude Code and Codex

#9

Post by mhitza »

jlund-molfese wrote: post #5
appplication wrote: post #3

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.

I 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.

Relinking the recent study which argues that many instructions in the context are not followed through 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.

Post reply on HN