From 7e5a6516a4d53d38cd8f36725ad311131effdfc0 Mon Sep 17 00:00:00 2001 From: Frank Tovar Date: Wed, 18 Mar 2026 00:46:14 +0100 Subject: [PATCH] Update agent compile guidance --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index bd5c445..5496150 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -13,6 +13,7 @@ Also see the other related technical documentation in the docs folder. - Always place each newly created class into its own file. The file name must match the class name. - When asked to begin working on a task, create a detailed implementation plan first, present the plan to the user, and ask for approval before beginning with the actual implementation. - When an task is finished, perform a code review to evaluate if the change is clean and maintainable with high software engineering standards. Iterate on the code and repeat the review process until satisfied. +- Check if the code compiles with a compile-only `dotnet build` to avoid artifact conflicts. - After the implementation is finished, verify all changed files, and run `python D:\Code\crlf.py $file1 $file2 ...` only for files you recognize, in order to normalize all line endings of all touched files to CRLF. - If there's documnentation present, always keep it updated. - At the end perform a git commit with a one-liner summary. \ No newline at end of file