Guidelines are useful when your coding style or other preferences differ from what the model typically produces. E.g. when we started using collection expressions in C# ([“foo”, “bar”]<\/strong>), some models were not very familiar with them, and kept changing them back into the older syntax (new string[]{“foo”, “bar”}<\/strong>). It’s not very difficult to decline such edits via the reviewing GUI or to tell “don’t change [] to new()<\/strong>“, but it’s annoying to do that every time.<\/p>\n A rather concise guideline like this fixed it once and for all:<\/p>\n Language models have no problem ignoring irrelevant instructions, so guidelines don’t have to make sense for every edit. If the guideline says “don’t change collection expressions” and the code outright doesn’t contain any collection expressions, the model will simply ignore it.<\/p>\n The only drawback is that all active guidelines contribute to the context window usage (and token costs), so if you want to define guidelines for a specific rare task, you can use AI techniques<\/a> instead.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" AI guidelines are a fairly simple concept. Every time you ask AI to do some edit, CodeVROOM includes them in<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[66],"tags":[],"_links":{"self":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/896"}],"collection":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/comments?post=896"}],"version-history":[{"count":2,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/896\/revisions"}],"predecessor-version":[{"id":904,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/896\/revisions\/904"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/media?parent=896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/categories?post=896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/tags?post=896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"https:\/\/sysprogs.com\/tutorials\/wp-content\/uploads\/2025\/07\/guidelines.png\")
<\/a>Guidelines can be enabled\/disabled globally by unchecking the corresponding checkbox, and you can also enable\/disable them for a particular editing session via the AI Context window:<\/p>\n<\/a>If you are running language models on a slow GPU and want to heavily reduce the prompt size, you can uncheck individual guidelines, and CodeVROOM will immediately show you how it affects the prompt.<\/p>\nTypical Use<\/h1>\n
If you encounter collection expressions in the code (e.g. [x, y] instead of new int[]{x, y}), do not change them back to old-style expressions. The C# compiler handles them correctly.<\/pre>\n