My agent.md to improve LLM-assisted code quality
fabiensanglard.net
My agent.md to improve LLM-assisted code quality
1–10 of 200 posts
Re: My agent.md to improve LLM-assisted code quality
#2Re: My agent.md to improve LLM-assisted code quality
#3Then this one really is a pattern that creates a lot of churn:
- Add a small, to the point, comment to explain what the block does and why. Use examples when possible. Propose ASCII drawings to explain complete systems.
The what _is_ the code.
Re: My agent.md to improve LLM-assisted code quality
#4A bunch of these should be enforce with linting, that way people who still hand-craft code get the same kind of feedback, e.g. Always use {}, even on a one-line "if" statement. & Keep function names short. Less than 30 characters. Then this one really is a pattern that creates a lot of churn: - Add a small, to the point, comment to explain what the block does and why . Use examples when possible. Propose ASCII drawin…
Re: My agent.md to improve LLM-assisted code quality
#5That way everyone benefits.
Re: My agent.md to improve LLM-assisted code quality
#6**Always use ASD-STE100 Simplified Technical English
Disclaimer: I saw this listed in some other HN post that I can' locate right away.
Re: My agent.md to improve LLM-assisted code quality
#7Just this one line in AGENTS.md has given better results to reduce if not eliminate verbosity and grandeur. **Always use ASD-STE100 Simplified Technical English Disclaimer: I saw this listed in some other HN post that I can' locate right away.
Re: My agent.md to improve LLM-assisted code quality
#8Re: My agent.md to improve LLM-assisted code quality
#9Even my second one, "Avoid decorative or section-header comments. Never use `----` or `====` as comment separators. Comments should explain only non-obvious behavior, rationale, constraints, or implementation details." seems to be ignored by models regularly, so I don't see the point.
But this is in my private harness. Perhaps other harnesses have better instruction following. My custom instructions are prepended to my first user message, not set as a system message.