AGENTS.md@configs/delta · diff
git:20260821.9d57cf6 to git:20260913.c59c4a8
23 added, 11 removed. Audit A to A.
# 🤖 Delta Agent Guidelines
## Communication
Always talk in ASD-STE100 Simplified Technical English. Always read CONTEXT.md files if present, and use their ubiquitous language.
## Session Management with tmux
- Run dev servers, tests, and interactive CLIs inside tmux with the **current directory name as the session name** for easy debugging:
+ Use tmux for long-running development servers, watch processes, and interactive CLIs. Use the **current directory name as the session name** for easy debugging:
```bash
SESSION=$(basename "$PWD")
tmux new -d -s "$SESSION" 2>/dev/null || true
# Run dev server with portless if available, otherwise fallback to npm
if command -v portless &>/dev/null; then
tmux send-keys -t "$SESSION" 'portless run npm run dev' Enter
else
tmux send-keys -t "$SESSION" 'npm run dev' Enter
fi
tmux capture-pane -p -t "$SESSION" -S -20 # check output
```
## 🔧 AI Tool Guidelines
- - Use the fff MCP tools for all file search operations instead of default tools.
- - Use the sem MCP tools for semantic version control and git operations.
- - When using bash commands for file/content search, prefer `fd` (fdfind) and `rg` (ripgrep) over standard `find` and `grep` for better performance and git-awareness.
+ - Prefer the fff MCP tools for file search operations when available; otherwise use the environment's native tools.
+ - Prefer the sem MCP tools for semantic version control and git operations when available; otherwise use the environment's native tools.
+ - When using shell commands for file or content search, prefer `fd` (fdfind) and `rg` (ripgrep) over standard `find` and `grep` for better performance and git awareness.
## Token Efficiency
- Keep responses concise and actionable; lead with conclusions, file paths, and verification.
- Scope searches and file reads to the task. Limit command output with filters and line ranges.
- Use `~/.local/bin/rtk` for supported shell commands when available; bypass it with `RTK_DISABLED=1` when raw output is required.
- Prefer `codebase-memory-mcp` graph tools for structural code discovery when available.
- Load supplemental guidance only when the task requires it. Start a fresh session when switching to unrelated work.
+ ## Decision and Safety
+
+ - Follow explicit user requests and the most specific applicable project instructions.
+ - Inspect relevant context, conventions, and existing tests before changing files.
+ - Prefer the simplest solution that fully meets the requirement. Avoid speculative abstractions and unrelated refactoring.
+ - Preserve existing behaviour unless a change is required; fix root causes rather than symptoms.
+ - Clearly distinguish verified facts from assumptions.
+ - Ask before destructive or irreversible operations.
+ - Do not expose secrets, credentials, personal data, or sensitive project details in responses, logs, or files.
+
+ ## Verification
+
+ - Run the most relevant available checks after changes, such as tests, typecheck, lint, formatting, or build.
+ - Report what was verified and identify checks that were not run.
+
## 📋 General Practices
- Read `~/.ai-tools/best-practices.md` only when the repository lacks equivalent guidance or the task needs its detailed workflow.
- Read `~/.ai-tools/MEMORY.md` and `~/.ai-tools/agent-memory.md` only when deciding whether or where to persist a learning.
- Read `~/.ai-tools/git-guidelines.md` before destructive or history-changing git operations.
- - Ask before destructive operations — don't guess safety
- - Code is communication — prefer clarity and simplicity
- - Self-documenting code through meaningful names and structure
- - Modular design that can evolve
- - Comments explain why, not what
- - Run typecheck, lint and biome on js/ts file changes after finish.
- - Prefer to use Bun to run scripts if possible, otherwise use tsx to run ts files.
+ - Prefer clear names and simple structure. Comments should explain why, not what.
+ - Keep designs modular where change is likely, without overengineering speculative needs.
+ - For JavaScript or TypeScript changes, run the relevant typecheck, lint, formatting, and tests. Use Biome when the project configures it.
+ - Prefer Bun when the project supports it; otherwise use the project's configured runtime and package manager.