7 ms·
Great stuff. AGENTS.md is not the ideal place for most of it though. Most of what is shown in this article can go in CODING_STANDARDS.md. The skills that I use
by gregwebs 24d ago
Great stuff. AGENTS.md is not the ideal place for most of it though. Most of what is shown in this article can go in CODING_STANDARDS.md. The skills that I use find this document when it is needed (writing and reviewing code) so it doesn't pollute context when code is being read.
I also have sub-agent reviews (both of a planning phase and the produced code) that would catch some of these problems and demand revisions. [1]
> - If the prompt indicates that a bug is being fixed, don't write the fix right away. First write the test. Observe it failing. Then write the fix. And observe the test passing.
I always use /tdd [2]. Occasionally it results in some silly tests, but it produces much lower defect code. Its not just for bugs.
[1] https://github.com/gregwebs/skills-sdlc/ https://github.com/gregwebs/skills-sdlc/
[2] https://github.com/mattpocock/skills/blob/main/skills/engineering/tdd/SKILL.md https://github.com/mattpocock/skills/blob/main/skills/engine...
- firemelt 23d agoanyone have coding stabdards for ruby ob rails code?