CrompyBlompers

A better analogy would have reduced required thought. But here we are.

My brain stuck on the inaccurate monkey comparison and caused unnecessary work to get past it and back onto the point you were making.

Most people seem to mean "Skills don't pollute the context window [with their entire contents]", they just elide the part in brackets.

There is no magic and people should be more precise when discussing skills.

Then go be an artist and leave the rest of us to tend our well oiled machines.

There's a ton of variation in golang code, as gofmt is not opinionated enough. As evidenced by the existence of golines[0] or gofumpt[1].

0: https://github.com/golangci/golines/

1: https://github.com/mvdan/gofumpt

The skills dirs have some necessary content (or so I assume):

https://github.com/DietrichGebert/ponytail/tree/main/skills

Gotcha, thx for the context.

Typically we'd see the second person "you/your/you're" used and not the third person ("flatpands") here, since you (tarr1124) are directly responding to their comment, as if in conversation with them. ie: "what you're pointing at..."

Otherwise it reads like you're ignoring them and talking around them.

Respectfully, did you use an LLM to write this comment? You're responding to flatpandas here. Having "what flatpands is pointing at..." is similar to the output of an LLM if you were to link to that comment and get a generated summary.

To disambiguate, this is not meant as “added a mode to the stock Camera app”, but rather “added a mode to the camera API that iOS developers can use”.