Untitled
Central Agent Guidance
Storage and loading route
Cross-project, VS Code on Windows. Single entry point: D:\AI-stuff\agents.md; supplementary files: D:\AI-stuff\AI-Steuerdateien. Do not copy these files into product repositories, project roots, or worktrees. Product code and project documentation in the relevant repository remain authoritative; historical control files are not active requirements.
At the start of a session, load the following deliberately:
- CoderTeam.md: all roles, review groups, and quality gates.
- GitHub Behavior.md: A1-A6, B1/B2/B5; B4 before remote writes/cleanup/agent experiments, A7 before public work, A8/A9 for CI/protection questions, B3/B6 for applicable problems, B7 for VS Code command approvals, C only for BatteryBuddy.
- Token Optimization.md: section 1; sections 2-5 in full before local translation.
- Lessons Learned.md: only task-relevant topics; measurement evidence only for research/cost questions.
When a project folder is opened separately, detection of the parent entry point is not guaranteed. Read it explicitly or refer to it through personal VS Code instructions; do not make project copies. Do not skip relevant sections when the task calls for them.
Mandatory guardrails
- Quality over speed; explain things clearly for beginners through intermediate experts. Comments should explain only non-obvious reasons. Review non-trivial decisions from at least three relevant roles, not necessarily using separate agents.
- Project changes: issue -> working branch -> PR to
dev; after a complete self-review,dev -> test; movetest -> mainonly after the user explicitly approves the specific tested state, every time. Central control-file changes stay local and outside product repositories. <ProjectName>-Intern: private, withdev,test, andmain.<ProjectName>-Public: public, with a description, curated final code, and executable release assets. Approve publication separately; it has its own history and is not a mirror/fork of the private repository.- Names are not proof: verify remotes, visibility, worktree, branch, current SHA, and approval according to B2. New projects inherit the process, not the framework, license, paths, or old approvals.
- Validate inputs, encrypt transport when required, protect secrets and user work; test appropriately and self-review. If an actual firewall/network block occurs, pause and ask; do not work around it.
- Use Ollama only for the verified serial translation route in Token Optimization.md. Do not use new models or run broad benchmarks without authorization; programming, tests, reviews, and GitHub/documentation administration remain in the Copilot workflow.
Leave a Comment