docs: add agent operating principles to AGENTS.md and CLAUDE.md

This commit is contained in:
Sipke Schoorstra 2026-05-06 12:44:27 +02:00
parent 80d3ad2b47
commit 3e43b85a2b
No known key found for this signature in database
GPG key ID: 5C10502B28A4268F
2 changed files with 14 additions and 0 deletions

View file

@ -18,6 +18,13 @@ Guidance for AI coding agents working in this repository.
- Do not delete generated-looking, artifact, or IDE files unless the task explicitly asks for cleanup.
- If the worktree contains unrelated user changes, leave them untouched.
## Agent Operating Principles
- Do not assume, hide confusion, or flatten uncertainty; surface questions, constraints, and tradeoffs explicitly.
- Write the minimum code that solves the defined problem; do not add speculative abstractions, features, or cleanup.
- Touch only the files and behavior required for the task; clean up only issues introduced by your own changes.
- Define success criteria before implementation, then iterate until the criteria are verified or clearly state what could not be verified.
## Build And Test Commands
- Build the default target: `./build.sh`

View file

@ -26,4 +26,11 @@ C# latest (`<LangVersion>latest</LangVersion>`), nullable reference types enable
- 002-graceful-shutdown: Added C# latest (`<LangVersion>latest</LangVersion>`), nullable reference types enabled, implicit usings enabled — per `src/Directory.Build.props`. + `Elsa.Workflows.Runtime`, `Elsa.Workflows.Runtime.Distributed`, `Elsa.Hosting.Management` (existing heartbeat), `Elsa.Http` and `Elsa.Scheduling` (first ingress-source adapters), `Elsa.Api.Common` (`ElsaEndpoint<TRequest, TResponse>` on FastEndpoints), `Elsa.Features` (`IShellFeature`), `Microsoft.Extensions.DependencyInjection`, `Elsa.Mediator`.
<!-- MANUAL ADDITIONS START -->
## Agent Operating Principles
- Do not assume, hide confusion, or flatten uncertainty; surface questions, constraints, and tradeoffs explicitly.
- Write the minimum code that solves the defined problem; do not add speculative abstractions, features, or cleanup.
- Touch only the files and behavior required for the task; clean up only issues introduced by your own changes.
- Define success criteria before implementation, then iterate until the criteria are verified or clearly state what could not be verified.
<!-- MANUAL ADDITIONS END -->