From 13e2dbbea0505407d168fcfc7b48f60f9de6fdb5 Mon Sep 17 00:00:00 2001 From: Julian lechner Date: Fri, 11 Sep 2026 14:43:36 +0200 Subject: [PATCH] feat(orchestration): add shared global instructions --- shared/global-instructions.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 shared/global-instructions.md diff --git a/shared/global-instructions.md b/shared/global-instructions.md new file mode 100644 index 0000000..7fdd31c --- /dev/null +++ b/shared/global-instructions.md @@ -0,0 +1,32 @@ +# Personal global instructions + +This instruction set is generated into the client-specific `AGENTS.md` and `CLAUDE.md` files. Do not edit generated copies. + +Always load and apply `rules/general.md` before starting any task. + +When programming, always load and apply `rules/security.md`. This includes implementing, modifying, debugging, reviewing, testing, and configuring software, scripts, hooks, infrastructure, and integrations. + +Detect the languages, frameworks, tools, and change areas from the repository and the requested work. Load every applicable rule file before editing. Load all matching files when multiple technologies apply. + +Load rule files when their subject applies: + +- rules/angular.md for Angular work. +- rules/typescript.md for TypeScript work. +- rules/csharp.md for C# or .NET work. +- rules/wpf.md for WPF work. +- rules/ui-ux.md for UI or UX decisions. +- rules/microsoft.md for Microsoft 365, Azure DevOps, or Teams work. +- rules/git.md for Git operations. +- rules/refactoring.md for refactoring work. +- rules/definition-of-done.md when validating completion. +- rules/decision-rule.md when requirements, behavior, or technical choices need to be evaluated. + +Apply instructions in this order: direct current user instructions; security and data-loss protections; applicable project instructions; these global rules; existing project conventions; agent preferences. + +Make evidence-based, reversible technical decisions independently. Ask when material uncertainty, multiple meaningful options, or high-impact irreversible effects remain. Ask about business behavior, user-visible behavior, UI, UX, APIs, database models, configuration formats, compatibility behavior, and other product decisions only when they are missing, ambiguous, contradictory, or open to interpretation. Implement explicitly specified behavior without asking again. + +Never modify existing documentation automatically. Ask before a code change that would make existing documentation inaccurate. Create no new documentation, code comments, change summaries, pull request descriptions, work item text, or release notes without explicit user approval. If a comment appears necessary, ask first. + +Project-specific instructions may specialize global defaults but must not weaken security or data-loss protections without explicit user approval. Direct user instructions have the highest priority for requested behavior. + +Use implementer for execution and architect when technical boundaries or design options need dedicated analysis. Invoke researcher, reviewer, or verifier only when independent work is likely to improve the outcome. Decide based on uncertainty, complexity, risk, blast radius, and verification value; do not invoke these roles automatically. Parallelize only genuinely independent work.