bc-code-intelligence-mcp 1.5.9 → 1.6.0

package/embedded-knowledge/domains/roger-reviewer/al-code-spacing-conventions.md

@@ -1,11 +1,21 @@
----
+---
 title: "AL Code Spacing and Indentation Conventions"
 domain: "roger-reviewer"
 difficulty: "beginner"
 bc_versions: "14+"
 tags: ["formatting", "indentation", "code-style", "readability"]
 prerequisites: ["al-syntax"]
----
+
+relevance_signals:
+  constructs: ["var", "begin", "end", "procedure", "trigger", "if", "then", "else", "for", "while", "case"]
+  keywords: ["spacing", "indentation", "4-space", "white space", "code style", "formatting"]
+  anti_pattern_indicators: ["inconsistent indentation", "mixed tabs/spaces", "excessive blank lines", "cramped formatting"]
+  positive_pattern_indicators: ["consistent 4-space indentation", "logical grouping", "clear visual hierarchy"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
+---
 # AL Code Spacing and Indentation Conventions
 
 ## Overview

package/embedded-knowledge/domains/roger-reviewer/al-comment-spacing-standards.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Apply consistent spacing around AL comments to improve
 implementation_steps: ["standardize-comment-spacing", "apply-consistent-patterns", "validate-readability"]
 validation_criteria: ["consistent-comment-spacing", "clear-documentation-separation"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["//"]
+  keywords: ["comment spacing", "documentation", "inline comment", "block comment", "comment delimiter"]
+  anti_pattern_indicators: ["inconsistent spacing", "cramped comments", "poor indentation in comments"]
+  positive_pattern_indicators: ["blank line before comments", "single space after delimiter", "consistent comment formatting"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Comment Spacing Standards

package/embedded-knowledge/domains/roger-reviewer/al-end-else-pairing.md

@@ -13,6 +13,16 @@ improvement_suggestion: "Properly pair end statements with else clauses to maint
 implementation_steps: ["identify-block-boundaries", "align-end-else-pairs", "validate-structure"]
 validation_criteria: ["correct-end-else-pairing", "clear-block-boundaries"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["if", "then", "else", "begin", "end"]
+  keywords: ["end else", "block structure", "conditional pairing", "scope closure", "syntax correctness"]
+  anti_pattern_indicators: ["missing end statements", "improper block closure", "ambiguous pairing"]
+  positive_pattern_indicators: ["close blocks completely before else", "aligned end-else pairs", "consistent indentation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.5
 ---
 
 # AL End Else Pairing

package/embedded-knowledge/domains/roger-reviewer/al-keyword-indentation-rules.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Apply consistent indentation rules for AL keywords to c
 implementation_steps: ["define-indentation-standards", "apply-keyword-rules", "validate-consistency"]
 validation_criteria: ["consistent-keyword-indentation", "clear-code-hierarchy"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["if", "else", "while", "for", "case", "begin", "end", "var", "procedure", "trigger", "table", "page", "codeunit"]
+  keywords: ["keyword indentation", "indentation hierarchy", "nesting level", "visual hierarchy", "code structure"]
+  anti_pattern_indicators: ["inconsistent indentation increments", "misaligned begin/end pairs", "random keyword positioning"]
+  positive_pattern_indicators: ["consistent increment size", "aligned block keywords", "scope reflection through indentation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Keyword Indentation Rules

package/embedded-knowledge/domains/roger-reviewer/al-line-start-keyword-positioning.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Position AL keywords at line start with consistent alig
 implementation_steps: ["identify-keyword-patterns", "apply-positioning-rules", "validate-alignment"]
 validation_criteria: ["consistent-keyword-positioning", "clear-structure-indication"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["if", "else", "begin", "end", "var", "procedure", "while", "for", "case"]
+  keywords: ["line start", "keyword positioning", "keyword anchoring", "structure markers", "visual structure"]
+  anti_pattern_indicators: ["inconsistent keyword alignment", "mid-line keyword placement", "random positioning"]
+  positive_pattern_indicators: ["line start positioning", "consistent alignment", "clear structure indication"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Line Start Keyword Positioning

package/embedded-knowledge/domains/roger-reviewer/al-separate-if-else-formatting.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Format if-else statements with clear separation to show
 implementation_steps: ["separate-conditional-blocks", "align-if-else-keywords", "validate-readability"]
 validation_criteria: ["clear-conditional-separation", "consistent-alignment"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["if", "then", "else", "begin", "end"]
+  keywords: ["if-else formatting", "conditional logic", "branch separation", "decision structure"]
+  anti_pattern_indicators: ["cramped if-else formatting", "inconsistent keyword alignment", "unclear branch boundaries"]
+  positive_pattern_indicators: ["clear keyword positioning", "appropriate spacing", "aligned block structures"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Separate If Else Formatting

package/embedded-knowledge/domains/roger-reviewer/al-standard-abbreviations.md

@@ -13,6 +13,16 @@ improvement_suggestion: "Use only Microsoft-approved abbreviations to maintain c
 implementation_steps: ["verify-platform-abbreviations", "apply-standard-patterns", "validate-consistency"]
 validation_criteria: ["platform-compliant-abbreviations", "consistent-usage"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["abbreviation", "No.", "Qty", "Amt", "Desc", "LCY", "FCY", "G/L", "VAT", "UOM", "BOM", "SKU", "Whse", "Invt", "Prod"]
+  anti_pattern_indicators: ["custom abbreviations", "inconsistent abbreviation forms", "ambiguous terms", "platform conflicts"]
+  positive_pattern_indicators: ["platform-compliant abbreviations", "consistent usage", "standard BC abbreviations"]
+
+applicable_object_types: ["table", "tableextension", "page", "pageextension", "codeunit", "report", "query"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Standard Abbreviations

package/embedded-knowledge/domains/roger-reviewer/al-statement-per-line-rule.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Write one AL statement per line to improve readability
 implementation_steps: ["separate-multiple-statements", "format-single-statements", "validate-clarity"]
 validation_criteria: ["one-statement-per-line", "improved-readability"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: [";"]
+  keywords: ["statement per line", "single statement", "line organization", "debugging", "readability"]
+  anti_pattern_indicators: ["multiple statements per line", "cramped code formatting", "complex compound statements"]
+  positive_pattern_indicators: ["single statement per line", "appropriate indentation", "clear statement separation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Statement Per Line Rule

package/embedded-knowledge/domains/roger-reviewer/al-unnecessary-else-elimination.md

@@ -14,6 +14,16 @@ implementation_steps: ["identify-redundant-else", "apply-early-exit-patterns", "
 validation_criteria: ["reduced-complexity", "improved-readability"]
 technical_areas: ["al-code"]
 samples: "samples/al-unnecessary-else-elimination.md"
+
+relevance_signals:
+  constructs: ["if", "then", "else", "exit", "Error"]
+  keywords: ["unnecessary else", "early return", "guard clause", "early exit", "reduced nesting"]
+  anti_pattern_indicators: ["else after exit", "else after Error", "redundant else block", "deep nesting"]
+  positive_pattern_indicators: ["early exit pattern", "guard clause", "linear flow", "reduced nesting"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Unnecessary Else Elimination

package/embedded-knowledge/domains/roger-reviewer/al-variable-declaration-order.md

@@ -14,6 +14,16 @@ implementation_steps: ["establish-declaration-order", "group-related-variables",
 validation_criteria: ["consistent-declaration-order", "improved-organization"]
 technical_areas: ["al-code"]
 samples: "samples/al-variable-declaration-order.md"
+
+relevance_signals:
+  constructs: ["var", "Record", "Codeunit", "Page", "Report", "Text", "Integer", "Decimal", "Boolean", "Dialog", "File"]
+  keywords: ["variable declaration", "declaration order", "variable grouping", "scope organization", "type ordering"]
+  anti_pattern_indicators: ["random ordering", "mixed types", "no grouping", "inconsistent patterns"]
+  positive_pattern_indicators: ["logical grouping", "related variables together", "consistent declaration order"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Variable Declaration Order

package/embedded-knowledge/domains/roger-reviewer/al-variable-naming-conventions.md

@@ -13,6 +13,16 @@ improvement_suggestion: "Apply consistent variable naming conventions to enhance
 implementation_steps: ["establish-naming-standards", "apply-consistent-patterns", "validate-conventions"]
 validation_criteria: ["consistent-naming-application", "improved-readability"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["var", "Record", "Codeunit", "Page", "Report", "Boolean", "Text", "Integer", "Decimal"]
+  keywords: ["variable naming", "naming convention", "CamelCase", "Temp prefix", "Is/Has/Can prefix", "Mgt suffix"]
+  anti_pattern_indicators: ["generic names", "misleading abbreviations", "type prefixes", "inconsistent casing", "Hungarian notation"]
+  positive_pattern_indicators: ["descriptive names", "consistent naming pattern", "business terms", "clear intent"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Variable Naming Conventions

package/embedded-knowledge/domains/roger-reviewer/begin-block-statement-clarity.md

@@ -5,6 +5,16 @@ difficulty: "beginner"
 bc_versions: "14+"
 tags: ["user-experience", "code-clarity", "begin-blocks", "developer-productivity", "code-comprehension"]
 prerequisites: ["al-syntax", "code-style"]
+
+relevance_signals:
+  constructs: ["begin", "end", "if", "then", "else", "while", "for", "repeat"]
+  keywords: ["begin block", "code clarity", "visual boundaries", "logical grouping", "scope clarity"]
+  anti_pattern_indicators: ["inconsistent block usage", "unclear boundaries", "unnecessary complexity", "missing logical grouping"]
+  positive_pattern_indicators: ["consistent application", "visual hierarchy", "purposeful grouping", "maintenance support"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 # Begin Block Statement Clarity for Developer Experience
 

package/embedded-knowledge/domains/roger-reviewer/begin-end-positioning-patterns.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Use consistent begin/end positioning for improved code
 implementation_steps: ["establish-team-standards", "configure-formatting-tools", "apply-consistently"]
 validation_criteria: ["consistent-positioning", "improved-readability", "team-adoption"]
 technical_areas: ["al-code", "formatting"]
+
+relevance_signals:
+  constructs: ["begin", "end", "procedure", "trigger"]
+  keywords: ["begin positioning", "end positioning", "block boundaries", "visual structure", "nesting visualization"]
+  anti_pattern_indicators: ["mixed positioning", "context-dependent formatting", "excessive compaction", "unclear boundaries"]
+  positive_pattern_indicators: ["consistent positioning", "logical grouping", "debugging support", "team standards"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # Begin/End Positioning in AL Code

package/embedded-knowledge/domains/roger-reviewer/binary-operator-line-positioning.md

@@ -1,11 +1,21 @@
----
+---
 title: "Binary Operator Line Positioning and Code Readability"
 domain: "roger-reviewer"
 difficulty: "beginner"
 bc_versions: "14+"
 tags: ["code-style", "operators", "readability", "formatting", "line-breaks"]
 prerequisites: ["al-syntax", "code-formatting"]
----
+
+relevance_signals:
+  constructs: ["and", "or", "+", "-", "*", "/", "=", "<>", "<", ">", "<=", ">="]
+  keywords: ["operator positioning", "line continuation", "leading operators", "multi-line expression", "visual alignment"]
+  anti_pattern_indicators: ["inconsistent positioning", "poor alignment", "trailing operators", "random line breaks"]
+  positive_pattern_indicators: ["leading operator pattern", "aligned continuation", "consistent indentation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
+---
 # Binary Operator Line Positioning and Code Readability
 
 ## Overview

package/embedded-knowledge/domains/roger-reviewer/boolean-expression-simplification-al.md

@@ -6,6 +6,16 @@ bc_versions: "14+"
 tags: ["boolean-expressions", "code-simplification", "readability", "performance", "refactoring"]
 prerequisites: ["al-syntax-basics", "conditional-logic"]
 samples: "samples/boolean-simplification-examples.md"
+
+relevance_signals:
+  constructs: ["and", "or", "not", "if", "then", "else", "=", "<>", "true", "false"]
+  keywords: ["boolean simplification", "De Morgan", "short-circuit evaluation", "double negative", "positive logic", "guard clause"]
+  anti_pattern_indicators: ["double negatives", "redundant conditions", "complex nested conditions", "not (not Condition)"]
+  positive_pattern_indicators: ["simplified boolean", "positive expression", "early exit", "guard clause"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "pageextension", "tableextension"]
+
+relevance_threshold: 0.5
 ---
 
 # Boolean Expression Simplification in AL

package/embedded-knowledge/domains/roger-reviewer/case-statement-error-handling-troubleshooting.md

@@ -1,11 +1,21 @@
----
+---
 title: "Case Statement Error Handling and Troubleshooting"
 domain: "roger-reviewer"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["case", "error-handling", "troubleshooting", "debugging"]
 samples: "samples/case-error-handling.md"
----
+
+relevance_signals:
+  constructs: ["case", "of", "else", "end", "Error", "Message"]
+  keywords: ["case error handling", "unhandled values", "else clause", "error message", "defensive programming", "graceful degradation"]
+  anti_pattern_indicators: ["missing else clause", "silent failures", "generic error messages", "no input validation"]
+  positive_pattern_indicators: ["mandatory else clause", "informative error messages", "input validation before case", "graceful degradation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "pageextension", "tableextension"]
+
+relevance_threshold: 0.6
+---
 # Case Statement Error Handling and Troubleshooting
 
 ## Overview

package/embedded-knowledge/domains/roger-reviewer/compound-statement-readability.md

@@ -1,4 +1,4 @@
----
+---
 title: "AL Compound Statement Readability Patterns"
 domain: "roger-reviewer"
 difficulty: "beginner"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["readability", "compound-statements", "code-style", "maintainability"]
 prerequisites: ["al-syntax-basics"]
 samples: "samples/compound-statement-readability.md"
----
+
+relevance_signals:
+  constructs: ["begin", "end", "if", "then", "else", "while", "for", "repeat", "until"]
+  keywords: ["compound statement", "begin-end block", "visual structure", "intent communication", "code consistency"]
+  anti_pattern_indicators: ["inconsistent block usage", "single statement without begin/end", "unclear scope"]
+  positive_pattern_indicators: ["consistent begin-end usage", "explicit block structure", "visual boundaries"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
+---
 # AL Compound Statement Readability Patterns
 
 ## Overview

package/embedded-knowledge/domains/roger-reviewer/lonely-repeat-statement-pattern.md

@@ -6,6 +6,16 @@ bc_versions: "14+"
 tags: ["code-formatting", "repeat-statement", "readability", "code-standards"]
 prerequisites: ["al-syntax-basics", "control-structures"]
 samples: "samples/lonely-repeat-examples.md"
+
+relevance_signals:
+  constructs: ["repeat", "until"]
+  keywords: ["lonely repeat", "repeat formatting", "until alignment", "loop structure", "visual connection"]
+  anti_pattern_indicators: ["isolated repeat", "misaligned until", "extra blank lines in repeat block"]
+  positive_pattern_indicators: ["connected repeat block", "aligned until keyword", "consistent indentation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "pageextension", "tableextension"]
+
+relevance_threshold: 0.4
 ---
 
 # Lonely Repeat Statement Pattern

package/embedded-knowledge/domains/roger-reviewer/testability-code-smells.md

@@ -9,6 +9,16 @@ related_topics:
   - "../alex-architect/testability-design-patterns.md"
   - "../quinn-tester/isolation-testing-patterns.md"
 source: "Adapted from Vjeko.com: Testing in isolation (Dec 2023)"
+
+relevance_signals:
+  constructs: ["Record", "HttpClient", "Get", "FindSet", "DeleteAll", "case"]
+  keywords: ["testability", "code smell", "tight coupling", "test isolation", "dependency injection", "abstraction", "mock", "test double"]
+  anti_pattern_indicators: ["direct BC table access", "hardcoded service calls", "DeleteAll in test", "mixed data access and logic", "setup switch"]
+  positive_pattern_indicators: ["interface abstraction", "dependency injection", "isolated business logic", "test doubles"]
+
+applicable_object_types: ["codeunit", "page", "table", "report"]
+
+relevance_threshold: 0.6
 ---
 # Testability Code Smells
 

package/embedded-knowledge/domains/sam-coder/al-formatting-consistency-patterns.md

@@ -13,6 +13,16 @@ improvement_suggestion: "Apply consistent formatting patterns across all AL code
 implementation_steps: ["establish-formatting-standards", "apply-consistent-patterns", "validate-uniformity"]
 validation_criteria: ["consistent-formatting-application", "improved-code-uniformity"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["formatting", "consistency", "indentation", "code-standards", "alignment", "keyword casing", "comment styles"]
+  anti_pattern_indicators: ["mixed formatting styles", "inconsistent indentation", "random keyword casing", "varied comment formatting"]
+  positive_pattern_indicators: ["consistent formatting", "uniform appearance", "standard patterns", "formatting standards"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "enum", "interface"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Formatting Consistency Patterns

package/embedded-knowledge/domains/sam-coder/al-line-comment-formatting.md

@@ -1,11 +1,21 @@
----
+---
 title: "AL Line Comment Formatting and Placement Patterns"
 domain: "sam-coder"
 difficulty: "beginner"
 bc_versions: "14+"
 tags: ["comments", "code-quality", "readability", "maintainability"]
 prerequisites: ["al-basics"]
----
+
+relevance_signals:
+  constructs: []
+  keywords: ["comments", "documentation", "readability", "line comment", "inline comment", "code documentation"]
+  anti_pattern_indicators: ["commenting obvious code", "excessive commenting", "outdated information", "poor grammar"]
+  positive_pattern_indicators: ["explains why", "business context", "edge cases", "performance notes"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "enum", "interface"]
+
+relevance_threshold: 0.4
+---
 # AL Line Comment Formatting and Placement Patterns
 
 ## Overview

package/embedded-knowledge/domains/sam-coder/al-lonely-repeat-pattern.md

@@ -14,6 +14,16 @@ improvement_suggestion: "Avoid lonely repeat statements by ensuring proper until
 implementation_steps: ["identify-repeat-patterns", "validate-until-conditions", "ensure-proper-structure"]
 validation_criteria: ["complete-repeat-until-pairs", "proper-loop-structure"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: ["repeat", "until"]
+  keywords: ["repeat-until", "loop", "control flow", "infinite loop", "termination", "loop exit"]
+  anti_pattern_indicators: ["repeat without until", "unreachable until conditions", "no loop variable progression", "infinite loop"]
+  positive_pattern_indicators: ["proper until condition", "reliable termination", "loop variable progression", "exit condition"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query"]
+
+relevance_threshold: 0.5
 ---
 
 # AL Lonely Repeat Pattern

package/embedded-knowledge/domains/sam-coder/al-named-parameter-pattern.md

@@ -14,6 +14,16 @@ implementation_steps: ["identify-complex-calls", "create-descriptive-variables",
 validation_criteria: ["improved-call-clarity", "reduced-parameter-errors"]
 technical_areas: ["al-code"]
 samples: "samples/al-named-parameter-pattern.md"
+
+relevance_signals:
+  constructs: []
+  keywords: ["named parameters", "parameter object", "procedure calls", "descriptive variables", "self-documenting", "parameter ordering"]
+  anti_pattern_indicators: ["magic numbers", "parameter soup", "type confusion", "inconsistent ordering", "literal values without names"]
+  positive_pattern_indicators: ["descriptive variable names", "parameter object", "logical grouping", "clear parameter purpose"]
+
+applicable_object_types: ["codeunit", "page", "table", "report"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Named Parameter Pattern

package/embedded-knowledge/domains/sam-coder/al-object-navigation-shortcuts.md

@@ -5,6 +5,16 @@ difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["navigation", "al-objects", "workspace", "symbol-search", "dependencies"]
 prerequisites: ["vs-code-al-shortcuts", "al-project-structure"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["navigation", "F12", "Go to Definition", "Find All References", "symbol search", "Peek Definition", "workspace", "object discovery"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["efficient navigation", "symbol-based navigation", "reference discovery", "dependency tracking"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "enum", "interface"]
+
+relevance_threshold: 0.3
 ---
 
 # AL Object Navigation Shortcuts

package/embedded-knowledge/domains/sam-coder/al-readability-optimization.md

@@ -13,6 +13,16 @@ improvement_suggestion: "Optimize AL code readability through strategic formatti
 implementation_steps: ["analyze-readability-factors", "apply-optimization-techniques", "validate-improvement"]
 validation_criteria: ["improved-code-readability", "reduced-cognitive-load"]
 technical_areas: ["al-code"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["readability", "cognitive load", "code comprehension", "visual hierarchy", "naming clarity", "logical organization"]
+  anti_pattern_indicators: ["dense code blocks", "unclear naming", "random organization", "inconsistent patterns", "unnecessary complexity"]
+  positive_pattern_indicators: ["clear visual hierarchy", "logical grouping", "strategic white space", "meaningful naming", "progressive complexity"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "enum", "interface"]
+
+relevance_threshold: 0.4
 ---
 
 # AL Readability Optimization

package/embedded-knowledge/domains/sam-coder/al-record-find-early-exit.md

@@ -14,6 +14,16 @@ implementation_steps: ["identify-record-operations", "apply-early-exit-patterns"
 validation_criteria: ["improved-performance", "reduced-database-load"]
 technical_areas: ["al-code", "database"]
 samples: "samples/al-record-find-early-exit.md"
+
+relevance_signals:
+  constructs: ["Find", "FindFirst", "FindLast", "FindSet", "Get", "IsEmpty", "exit"]
+  keywords: ["early exit", "guard clause", "record existence", "database query", "performance optimization"]
+  anti_pattern_indicators: ["assumed existence", "nested processing", "ignored return values", "processing without Find verification"]
+  positive_pattern_indicators: ["if not Find then exit", "guard clause", "early return", "existence check before processing"]
+
+applicable_object_types: ["codeunit", "page", "table", "report"]
+
+relevance_threshold: 0.6
 ---
 
 # AL Record Find Early Exit

package/embedded-knowledge/domains/sam-coder/command-queue-pattern-al.md

@@ -7,6 +7,16 @@ tags: ["command-queue", "async-processing", "message-patterns", "queue-managemen
 prerequisites: ["queue-basics", "command-pattern", "async-programming"]
 samples: "samples/command-queue-pattern.md"
 related_topics: ["task-scheduler-pattern-implementation", "event-bridge-pattern-al"]
+
+relevance_signals:
+  constructs: ["Codeunit.Run", "TaskScheduler", "JobQueue"]
+  keywords: ["command queue", "async processing", "queue management", "FIFO", "priority queue", "batch processing", "retry", "dead letter"]
+  anti_pattern_indicators: ["queue overflow", "command coupling", "processing bottlenecks", "unbounded queue"]
+  positive_pattern_indicators: ["idempotent commands", "queue health monitoring", "retry mechanism", "command encapsulation"]
+
+applicable_object_types: ["codeunit", "table"]
+
+relevance_threshold: 0.5
 ---
 
 # Command Queue Pattern in AL

package/embedded-knowledge/domains/sam-coder/deleteall-alternative-implementation.md

@@ -1,11 +1,21 @@
----
+---
 title: "DeleteAll Alternative Implementation"
 domain: "sam-coder"
 difficulty: "advanced"
 bc_versions: "14+"
 tags: ["deleteall", "alternatives", "implementation", "patterns"]
 samples: "samples/deleteall-alternative-implementation.md"
----
+
+relevance_signals:
+  constructs: ["DeleteAll", "Delete", "OnDelete"]
+  keywords: ["DeleteAll alternative", "bulk delete", "SQL DELETE", "performance optimization", "custom deletion", "batch processing"]
+  anti_pattern_indicators: ["business logic neglect", "premature optimization", "incomplete implementation", "bypassing triggers incorrectly"]
+  positive_pattern_indicators: ["controlled business logic", "batch record processing", "optimized transaction boundaries", "hybrid approach"]
+
+applicable_object_types: ["codeunit", "table"]
+
+relevance_threshold: 0.6
+---
 # DeleteAll Alternative Implementation
 
 ## Overview

package/embedded-knowledge/domains/sam-coder/deleteall-method-usage.md

@@ -6,6 +6,16 @@ bc_versions: "14+"
 tags: ["deleteall", "data-manipulation", "triggers"]
 prerequisites: ["table-basics", "record-management"]
 samples: "samples/deleteall-usage.md"
+
+relevance_signals:
+  constructs: ["DeleteAll", "OnDelete", "Delete"]
+  keywords: ["DeleteAll", "bulk deletion", "data manipulation", "trigger execution", "data integrity", "cascade delete"]
+  anti_pattern_indicators: ["DeleteAll for performance", "bypassing OnDelete", "insufficient error handling", "assumed trigger bypass"]
+  positive_pattern_indicators: ["proper OnDelete triggers", "transaction management", "validation before delete", "appropriate filters"]
+
+applicable_object_types: ["codeunit", "table"]
+
+relevance_threshold: 0.6
 ---
 # DeleteAll Method Usage
 

package/embedded-knowledge/domains/sam-coder/deleteall-trigger-execution.md

@@ -6,6 +6,16 @@ bc_versions: "14+"
 tags: ["deleteall", "triggers", "ondelete", "execution-flow"]
 prerequisites: ["deleteall-method-usage", "table-triggers", "transaction-management"]
 samples: "samples/deleteall-triggers.md"
+
+relevance_signals:
+  constructs: ["DeleteAll", "OnDelete", "Delete", "trigger"]
+  keywords: ["OnDelete trigger", "trigger execution", "cascade delete", "audit trail", "validation", "transaction management"]
+  anti_pattern_indicators: ["performance-blind trigger design", "inadequate error handling", "external system dependencies in triggers", "complex trigger logic"]
+  positive_pattern_indicators: ["focused OnDelete triggers", "efficient cascade patterns", "proper error handling", "testable triggers"]
+
+applicable_object_types: ["codeunit", "table"]
+
+relevance_threshold: 0.6
 ---
 # DeleteAll Trigger Execution
 

package/embedded-knowledge/domains/sam-coder/event-bridge-pattern-al.md

@@ -7,6 +7,16 @@ tags: ["event-bridge", "event-routing", "message-patterns", "loose-coupling"]
 prerequisites: ["event-basics", "publisher-subscriber", "interface-implementation"]
 samples: "samples/event-bridge-pattern.md"
 related_topics: ["event-payload-design-patterns", "command-queue-pattern-al"]
+
+relevance_signals:
+  constructs: ["IntegrationEvent", "BusinessEvent", "EventSubscriber"]
+  keywords: ["event bridge", "event routing", "loose coupling", "event transformation", "central event hub", "dynamic routing"]
+  anti_pattern_indicators: ["bridge complexity", "performance bottlenecks", "tight coupling through bridge"]
+  positive_pattern_indicators: ["flexible event routing", "event transformation", "dynamic routing rules", "asynchronous processing"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
 ---
 
 # Event Bridge Pattern in AL

package/embedded-knowledge/domains/sam-coder/event-payload-design-patterns.md

@@ -7,6 +7,16 @@ tags: ["event-payload", "message-design", "data-patterns", "serialization"]
 prerequisites: ["event-fundamentals", "data-structures", "json-handling"]
 samples: "samples/event-payload-design.md"
 related_topics: ["event-bridge-pattern-al", "command-queue-pattern-al"]
+
+relevance_signals:
+  constructs: ["IntegrationEvent", "BusinessEvent", "JsonObject", "JsonToken"]
+  keywords: ["event payload", "message design", "serialization", "versioning", "envelope pattern", "data completeness"]
+  anti_pattern_indicators: ["payload bloat", "breaking changes", "inconsistent structure", "unnecessary data"]
+  positive_pattern_indicators: ["standardized envelopes", "payload versioning", "backward compatibility", "clear field names"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.5
 ---
 
 # Event Payload Design Patterns