From f04f4aa08a93685a941b2aa17ce633da3486a955 Mon Sep 17 00:00:00 2001 From: Frank Tovar Date: Thu, 2 Apr 2026 00:52:27 +0200 Subject: [PATCH] Updated agents --- AGENTS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 7ad7507..591632d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -10,8 +10,8 @@ Also see the other related technical documentation: README.md. - Before beginning with the edit phase, always present a plan first. Only begin editing after the user approves the plan. - 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, and evaluate if a FAQ entry would help the users, serving as public documentation for this project. -- After every frontend change, verify the results using playwright. +- After every iteration, update all related documentation according to the change. +- 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. - If you find unexpected changes in the code (deletions, changes, diff results that were not communicated), never revert them and never restore the old state. Assume that those changes happened with intent.