I disagree with the less than 30 characters. Im against restricting anything related to code length this goes for function names and length, file length ect.

I disagree with the less than 30 characters. Im against restricting anything related to code length this goes for function names and length, file length ect. I rather the dots be as close as possible than trust the agent connects the dots. I dont care if the file is 5000 lines I rather the agent reads one file and get all the context than trust it will read all the need files. I see so many review skills that puts hard limits on these thing and it just bad. The function name shouldn't be limited they should be as clear as possible and if for some reason it over 30 chars so be it. I want to read the function name and the logic and it match exactly. I don't want the agent being lazy because of some limit I set. In fact I force my agents to write long functions because I specifically tell it not to break out repeated code that doesn't actually deserve a function. A check on a function input doesn't need to be a function. A auth guard doesn't need to be it own function. types.go types.ts absolutely the worst file to see in any code base. Put the type next to the code that uses it.