diff --git a/AGENTS.md b/AGENTS.md
index 6932b70..20897d0 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,14 +1,16 @@
 # Agent Guide — Pick'n'Play
 
-Also see the other related files: API.md, IIS.md, SPEC.md
+Also see the other related technical documentation: API.md, IIS.md, SPEC.md, README.md.
+Also see the user-facing documentation: per-language md files in wwwroot/data/i18n/faq
 
 ## Rules
 
-- This is a Windows environment, WSL is not installed (i.e. sed is not available). You're running under PowerShell 7.5.4. Due to platform restrictions, file deletions are not possible. Replacing the entire file content via a context diff is a viable alternative. PowerShell doesn't support bash-style heredocs, run Python code using python -c with inline commands instead of python - <<'PY'.
-- If complex scripts need to be executed, consider using python. It's installed.
+- This is a Windows environment, WSL is not installed (i.e. sed is not available). You're running under PowerShell 7.5.4. Due to platform restrictions, file deletions are not possible. Replacing the entire file content via a context diff is a viable alternative. 
+- PowerShell doesn't support bash-style heredocs. If complex scripts need to be executed, consider using python. Run Python code using python -c with inline commands instead of python - <<'PY'.
 - web.config in the server is different than locally, it must be exluded from deployment.
 - After every iteration, evaluate if the test coverage would fall below 100%, and write tests if necessary.
 - After every iteration, run "dotnet test GameList.Tests/GameList.Tests.csproj" and make sure 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 iteration, do a git commit with a brief summary of the changes as a commit message.
 - 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.
 - After changing the backend, feel free run "dotnet build" and "dotnet ef database update". If this is blocked by a running dotnet process, feel free to kill the process and retry the operations once.