From b3cde614e70c419955e0500f295d6c0910100e7e Mon Sep 17 00:00:00 2001 From: Frank Tovar Date: Sun, 5 Apr 2026 00:05:16 +0200 Subject: [PATCH] updated AGENTS.md --- AGENTS.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index 46b37cc..839bc89 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -12,6 +12,8 @@ Also see the other related technical documentation: README.md. - After every iteration, evaluate if the test coverage would fall below 100%, and write tests if necessary. - After every iteration, run "scripts/ci-local.ps1" and ensure that nothing broke. - After every iteration, update all related documentation according to the change. + - Update the wording of touched concerns instead of introducing incremental change reports + - The documentation should always represent the current state in its entirety and not derail into a historical development log. - After every frontend change, verify the results using an ephemeral playwright. - After every iteration, do a git commit with a brief summary of the changes as a commit message. - Keep changes small and commit often. If one iteration encompasses many smaller tasks with more than one commit, create a git branch and do the commits there. Let me review the branch before merging it back to master.