docs(rules): clarify just-in-time loading
CI / Capabilities and shell quality (push) Failing after 11s
CI / Python tests and compilation (push) Failing after 8s
CI / Build and inspect generated packages (push) Skipped
CI / Bash integration and installation guards (push) Skipped
CI / Installed client configuration smoke tests (push) Skipped
CI / Qwen retrieval integration (push) Skipped
CI / PowerShell tests on Ubuntu (push) Failing after 15s
CI / CI configuration security checks (push) Successful in 4s
CI / Capabilities and shell quality (push) Failing after 11s
CI / Python tests and compilation (push) Failing after 8s
CI / Build and inspect generated packages (push) Skipped
CI / Bash integration and installation guards (push) Skipped
CI / Installed client configuration smoke tests (push) Skipped
CI / Qwen retrieval integration (push) Skipped
CI / PowerShell tests on Ubuntu (push) Failing after 15s
CI / CI configuration security checks (push) Successful in 4s
This commit is contained in:
1 parent
3fcc2aa709
commit
d5c2ca556b
1 file changed
+3
-1
@@ -6,7 +6,9 @@ For credentials, run the child command through `~/.my-ai-configuration/bin/with-
|
||||
|
||||
## Loading rules
|
||||
|
||||
Detect affected technologies and concerns. Load every applicable rule: Codex reads its path; Claude invokes its `rules-*` skill. For directory indexes, load only matching topic rules listed there.
|
||||
Load rules just in time. First identify the changed area, languages, frameworks, tools, and security or workflow concerns from the task and nearby files. Then load the mandatory baseline and only rules whose triggers match; never preload or recursively read the complete rules tree.
|
||||
|
||||
For Codex, read the listed rule path directly. For Claude, invoke the matching `rules-*` skill by its exact name. When a technology directory applies, load its index skill/file first, then load only the topic skills/files that match the work. An index is a small routing map, not a request to load every linked topic. Load cross-cutting rules independently when their stated trigger applies. If a needed rule is not listed or installed, continue with applicable rules and repository conventions.
|
||||
|
||||
Every code, configuration, infrastructure, review, test, script, hook, or integration task: `rules/security/index.md` / `rules-security`.
|
||||
|
||||
|
||||
Reference in new issue
Block a user