diff --git a/CHANGELOG.md b/CHANGELOG.md index ded3c1bc..24a5e102 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,8 @@ not per individual commit. ### Changed +- The always-loaded core rules now carry the engineering practices from the `constraints` skill, + so agents get them without loading the skill. - The orchestrators (`konductor`, `konductor-mux-orchestrator`, `konductor-cmux-orchestrator`) may now read files, search the codebase, run read-only shell commands, and answer lookup questions themselves instead of spawning a specialist for each. One table in diff --git a/context/k-core-rules.md b/context/k-core-rules.md index f0446b71..c4dfea2f 100644 --- a/context/k-core-rules.md +++ b/context/k-core-rules.md @@ -18,3 +18,14 @@ These rules apply to every Konductor agent in every interaction. Violating a NEV ## Writing habits In sentences you write or rewrite, do not use em or en dashes, AI vocabulary, or filler, even when nearby text does (see the `humanize-writing` skill for how to rewrite them). This is about writing habits; code and doc conventions still follow the codebase. The user's explicit request, a project's explicit style guide, or a document-specific checker skill takes precedence. Leave text you are not changing as is, and never restyle code, existing string literals, or quoted text. + +## Engineering practices + +- Read the whole file before you edit it. +- Follow the patterns and conventions already in the codebase. +- Keep backward compatibility unless the user approves a breaking change. +- Comment non-obvious logic with the why, not the what. +- When you add or change logging in service code, make it structured and include correlation IDs; elsewhere follow the codebase's existing logging style. +- If you cannot explain the cause chain from root cause to symptom, research first and fix second. +- When a claim matters to a decision and you have not verified it, say whether it rests on documented knowledge (you read the code or docs), inference, or a guess. +- Before calling a code change done, confirm the tests pass, not only that the code compiles. An orchestrator gets that evidence from the specialist rather than running the tests. diff --git a/docs/index.html b/docs/index.html index fe428588..7cbb65b5 100644 --- a/docs/index.html +++ b/docs/index.html @@ -390,7 +390,7 @@