bc-code-intelligence-mcp 1.5.9 → 1.6.1

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

package/embedded-knowledge/domains/sam-coder/generic-method-patterns-al.md

@@ -7,6 +7,16 @@ tags: ["generic-methods", "type-safety", "code-reuse", "al-generics"]
 prerequisites: ["al-basics", "interface-implementation", "advanced-al-features"]
 samples: "samples/generic-method-patterns.md"
 related_topics: ["type-safe-operations-al", "template-method-pattern-al"]
+
+relevance_signals:
+  constructs: ["interface", "Variant", "RecordRef", "FieldRef"]
+  keywords: ["generic methods", "type-safe", "code reuse", "type parameter", "constraint", "type inference"]
+  anti_pattern_indicators: ["over-generalization", "constraint misuse", "performance degradation", "complex type hierarchies"]
+  positive_pattern_indicators: ["type-safe algorithms", "generic factory", "interface-based generics", "meaningful type parameters"]
+
+applicable_object_types: ["codeunit", "interface"]
+
+relevance_threshold: 0.5
 ---
 
 # Generic Method Patterns in AL

package/embedded-knowledge/domains/sam-coder/manual-binding-conditional-subscribers.md

@@ -6,6 +6,16 @@ bc_versions: "16+"
 tags: ["events", "binding", "conditional", "runtime"]
 prerequisites: ["event-subscriber-basics", "binding-patterns"]
 samples: "samples/manual-binding.md"
+
+relevance_signals:
+  constructs: ["EventSubscriber", "BindSubscription", "UnbindSubscription"]
+  keywords: ["manual binding", "conditional subscriber", "runtime binding", "event registration", "feature toggle", "multi-tenant"]
+  anti_pattern_indicators: ["failed deregistration", "registration failures", "inconsistent binding state", "missing lifecycle management"]
+  positive_pattern_indicators: ["conditional event processing", "dynamic binding", "feature-flag-controlled", "explicit lifecycle management"]
+
+applicable_object_types: ["codeunit"]
+
+relevance_threshold: 0.6
 ---
 # Manual Binding for Conditional Event Subscribers
 

package/embedded-knowledge/domains/sam-coder/nested-compound-best-practices.md

@@ -6,6 +6,16 @@ bc_versions: "14+"
 tags: ["nested-statements", "code-organization", "readability", "complexity-management"]
 prerequisites: ["compound-statement-readability", "al-control-flow"]
 samples: "samples/nested-compound-best-practices.md"
+
+relevance_signals:
+  constructs: ["begin", "end", "if", "then", "else", "while", "repeat"]
+  keywords: ["nested statements", "compound blocks", "nesting depth", "code organization", "complexity management", "readability"]
+  anti_pattern_indicators: ["deep nesting", "excessive complexity", "more than three levels", "cognitive overload"]
+  positive_pattern_indicators: ["depth limitation", "logical organization", "strategic extraction", "consistent formatting"]
+
+applicable_object_types: ["codeunit", "page", "table", "report"]
+
+relevance_threshold: 0.5
 ---
 # AL Nested Compound Statement Best Practices
 

package/embedded-knowledge/domains/sam-coder/single-to-compound-conversion.md

@@ -1,4 +1,4 @@
----
+---
 title: "Converting AL Single Statements to Compound Blocks"
 domain: "sam-coder"
 difficulty: "beginner"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["refactoring", "compound-statements", "code-conversion", "development-workflow"]
 prerequisites: ["al-syntax-basics", "compound-statement-readability"]
 samples: "samples/single-to-compound-conversion.md"
----
+
+relevance_signals:
+  constructs: ["begin", "end", "if", "then", "else", "while", "repeat"]
+  keywords: ["refactoring", "compound statements", "code conversion", "begin-end blocks", "single statement", "future-proofing"]
+  anti_pattern_indicators: ["single statement without begin-end", "if-then without block", "inconsistent patterns"]
+  positive_pattern_indicators: ["compound block structure", "explicit begin-end", "consistent refactoring", "safe transformation"]
+
+applicable_object_types: ["codeunit", "page", "table", "report"]
+
+relevance_threshold: 0.4
+---
 # Converting AL Single Statements to Compound Blocks
 
 ## Overview

package/embedded-knowledge/domains/sam-coder/template-method-pattern-al.md

@@ -7,6 +7,16 @@ tags: ["template-method", "behavioral-patterns", "algorithm-structure", "inherit
 prerequisites: ["object-orientation-al", "inheritance-patterns", "virtual-methods"]
 samples: "samples/template-method-pattern.md"
 related_topics: ["business-process-template-patterns", "type-safe-operations-al"]
+
+relevance_signals:
+  constructs: ["interface", "implements", "procedure"]
+  keywords: ["template method", "algorithm skeleton", "extension points", "inheritance", "virtual method", "behavioral pattern"]
+  anti_pattern_indicators: ["template complexity", "inflexible design", "too many extension points"]
+  positive_pattern_indicators: ["stable algorithm framework", "customizable steps", "invariant operations", "clear extension points"]
+
+applicable_object_types: ["codeunit", "interface"]
+
+relevance_threshold: 0.5
 ---
 
 # Template Method Pattern in AL

package/embedded-knowledge/domains/sam-coder/testfield-patterns.md

@@ -1,4 +1,4 @@
----
+---
 title: "TestField Best Practices and Patterns"
 domain: "sam-coder"
 difficulty: "intermediate"
@@ -6,7 +6,17 @@ bc_versions: "14+"
 tags: ["best-practices", "validation", "code-quality", "maintainability"]
 prerequisites: ["testfield-basic-syntax", "testfield-error-handling"]
 samples: "samples/testfield-patterns.md"
----
+
+relevance_signals:
+  constructs: ["TestField", "FieldError", "Error"]
+  keywords: ["TestField", "validation", "mandatory field", "data integrity", "field validation", "status-driven validation"]
+  anti_pattern_indicators: ["over-validation", "mixed concerns", "performance-blind validation", "context-blind validation"]
+  positive_pattern_indicators: ["fail fast", "logical validation grouping", "context-appropriate validation", "progressive validation"]
+
+applicable_object_types: ["codeunit", "page", "table"]
+
+relevance_threshold: 0.6
+---
 # TestField Best Practices and Patterns
 
 ## Overview

package/embedded-knowledge/domains/sam-coder/type-safe-operations-al.md

@@ -7,6 +7,16 @@ tags: ["type-safety", "compile-time-validation", "strong-typing", "error-prevent
 prerequisites: ["al-data-types", "variable-declaration", "procedure-design"]
 samples: "samples/type-safe-operations.md"
 related_topics: ["generic-method-patterns-al", "template-method-pattern-al"]
+
+relevance_signals:
+  constructs: ["Enum", "interface", "Option", "Record"]
+  keywords: ["type safety", "compile-time validation", "strong typing", "type-safe", "explicit type declarations", "enumeration"]
+  anti_pattern_indicators: ["over-engineering types", "implicit conversion", "type mismatch", "weak typing"]
+  positive_pattern_indicators: ["strongly-typed identifiers", "type-safe enumerations", "explicit type declarations", "compile-time checking"]
+
+applicable_object_types: ["codeunit", "table", "enum", "interface"]
+
+relevance_threshold: 0.5
 ---
 
 # Type-Safe Operations in AL

package/embedded-knowledge/domains/sam-coder/vs-code-al-keyboard-shortcuts.md

@@ -5,6 +5,16 @@ difficulty: "beginner"
 bc_versions: "14+"
 tags: ["vs-code", "productivity", "shortcuts", "al-extension", "navigation"]
 prerequisites: ["vs-code-setup", "al-extension-basics"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["keyboard shortcuts", "VS Code", "productivity", "IntelliSense", "debugging", "F12", "Ctrl+Space", "navigation"]
+  anti_pattern_indicators: []
+  positive_pattern_indicators: ["muscle memory", "coding flow", "efficient navigation", "shortcut mastery"]
+
+applicable_object_types: ["codeunit", "page", "table", "report", "query", "xmlport", "enum", "interface"]
+
+relevance_threshold: 0.3
 ---
 
 # VS Code AL Extension Keyboard Shortcuts

package/embedded-knowledge/domains/seth-security/al-temporary-table-safety.md

@@ -14,6 +14,16 @@ implementation_steps: ["validate-data-scope", "implement-secure-cleanup", "test-
 validation_criteria: ["secure-data-handling", "proper-memory-cleanup"]
 technical_areas: ["al-code", "data-management"]
 samples: "samples/al-temporary-table-safety.md"
+
+relevance_signals:
+  constructs: ["IsTemporary", "DeleteAll", "ModifyAll", "Insert", "Delete", "Modify", "Reset", "Copy"]
+  keywords: ["temporary table", "in-memory", "data leakage", "memory management", "session isolation", "security context", "data protection", "cleanup", "scope management"]
+  anti_pattern_indicators: ["persistent temporary data", "permission bypass", "cross-session leakage", "uncontrolled scope", "failing to clear"]
+  positive_pattern_indicators: ["secure initialization", "permission validation", "explicit clearing", "try-finally", "error handling cleanup", "minimal data", "data filtering"]
+
+applicable_object_types: ["codeunit", "table", "page", "report"]
+
+relevance_threshold: 0.7
 ---
 
 # AL Temporary Table Safety

package/embedded-knowledge/domains/seth-security/api-permission-model.md

@@ -1,11 +1,21 @@
----
+---
 title: "API Page Permission Model"
 domain: "seth-security"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["api-permissions", "access-control", "security"]
 samples: "samples/api-permission-model.md"
----
+
+relevance_signals:
+  constructs: ["APIPublisher", "APIGroup", "APIVersion", "ODataKeyFields", "EntityName", "EntitySetName", "Permissions", "TableData"]
+  keywords: ["API page", "OData", "permission model", "access control", "service account", "authentication", "authorization", "field-level security", "tenant isolation", "compliance", "audit"]
+  anti_pattern_indicators: ["missing permissions", "no authentication", "unprotected API", "exposed sensitive fields", "bypass security"]
+  positive_pattern_indicators: ["least privilege", "defense in depth", "permission sets", "field permissions", "audit trail", "service account", "OAuth"]
+
+applicable_object_types: ["page", "permissionset", "codeunit"]
+
+relevance_threshold: 0.7
+---
 # API Page Permission Model
 
 ## Overview

package/embedded-knowledge/domains/seth-security/istemporary-safeguard-pattern.md

@@ -1,11 +1,21 @@
----
+---
 title: "IsTemporary Table Safeguard Pattern for Data Protection"
 domain: "seth-security"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["data-protection", "temporary-tables", "safeguards", "data-integrity", "error-prevention"]
 prerequisites: ["al-tables", "data-access-patterns"]
----
+
+relevance_signals:
+  constructs: ["IsTemporary", "DeleteAll", "ModifyAll", "Insert", "Delete", "Modify", "Error"]
+  keywords: ["temporary table", "safeguard", "data protection", "bulk operation", "validation gate", "error prevention", "permanent table", "database safety"]
+  anti_pattern_indicators: ["skipping validation", "silent failure", "late validation", "generic error handling", "bypassing IsTemporary check"]
+  positive_pattern_indicators: ["early validation", "clear error messages", "conditional operations", "defensive programming", "precondition check"]
+
+applicable_object_types: ["codeunit", "table", "page", "report"]
+
+relevance_threshold: 0.7
+---
 # IsTemporary Table Safeguard Pattern for Data Protection
 
 ## Overview

package/embedded-knowledge/domains/shared/al-file-naming-conventions.md

@@ -1,146 +1,156 @@
----
-title: "AL File Naming Conventions"
-domain: ["sam-coder", "roger-reviewer"]
-difficulty: "beginner"
-bc_versions: "14+"
-tags: ["file-naming", "conventions", "code-style", "organization"]
-type: "improvement-pattern"
-category: "code-organization"
-pattern_type: "good"
-severity: "high"
-impact_level: "medium"
-improvement_suggestion: "Apply consistent AL file naming conventions following alguidelines.dev standards"
-implementation_steps: ["identify-object-name", "apply-object-type-suffix", "validate-naming-pattern"]
-validation_criteria: ["consistent-naming-application", "standards-compliance"]
-technical_areas: ["al-code", "file-organization"]
-related_topics: ["al-variable-naming-conventions", "al-standard-abbreviations"]
----
-
-# AL File Naming Conventions
-
-## Overview
-
-AL file naming conventions ensure consistent project organization and improve developer experience. Following standardized patterns makes codebases more maintainable and professional.
-
-**Source**: Based on [alguidelines.dev Rule #2: File Naming Conventions](https://alguidelines.dev/docs/vibe-coding/al-naming-conventions/)
-
-**Key Principle**: File names should be descriptive and match the AL object name within the files using the pattern `<ObjectName>.<ObjectType>.al`.
-
-## Standard File Naming Pattern
-
-### Core Pattern: `<ObjectName>.<ObjectType>.al`
-
-**Table Extensions:**
-```
-✅ CORRECT: CustomerExt.TableExt.al
-✅ CORRECT: SalesHeaderExt.TableExt.al
-❌ WRONG: Tab-Ext50100.CustomerExt.al
-❌ WRONG: TableExt50100.CustomerExt.al
-```
-
-**Page Extensions:**
-```
-✅ CORRECT: CustomerCardExt.PageExt.al
-✅ CORRECT: InventorySetupExt.PageExt.al
-❌ WRONG: Pag-Ext50100.CustomerCardExt.al
-❌ WRONG: PageExt50100.CustomerCardExt.al
-```
-
-**Codeunits:**
-```
-✅ CORRECT: CustomerCommentsManager.Codeunit.al
-✅ CORRECT: PostSalesInvoice.Codeunit.al
-❌ WRONG: Cod50100.CustomerCommentsManager.al
-❌ WRONG: Codeunit50100.CustomerCommentsManager.al
-```
-
-**Event Subscribers:**
-```
-✅ CORRECT: SalesEventsSubscriber.Codeunit.al
-✅ CORRECT: CustomerEventsHandler.Codeunit.al
-```
-
-## Object Type Suffixes
-
-### Standard Suffixes
-- **Tables**: `.Table.al`
-- **Table Extensions**: `.TableExt.al`
-- **Pages**: `.Page.al`
-- **Page Extensions**: `.PageExt.al`
-- **Page Customizations**: `.PageCust.al`
-- **Reports**: `.Report.al`
-- **Report Extensions**: `.ReportExt.al`
-- **Codeunits**: `.Codeunit.al`
-- **Queries**: `.Query.al`
-- **XMLports**: `.XMLport.al`
-- **Enums**: `.Enum.al`
-- **Enum Extensions**: `.EnumExt.al`
-- **Interfaces**: `.Interface.al`
-- **Control Add-ins**: `.ControlAddin.al`
-- **Dotnet**: `.Dotnet.al`
-- **Profiles**: `.Profile.al`
-- **Permission Sets**: `.PermissionSet.al`
-- **Permission Set Extensions**: `.PermissionSetExt.al`
-
-## Best Practices
-
-### Object Name Guidelines
-- **Use Pascal Case**: CustomerCommentsManager (not customercommentsmanager)
-- **Be Descriptive**: Clearly indicate object purpose
-- **Avoid Abbreviations**: Use full words unless standard BC terms
-- **Include Context**: For extensions, indicate what you're extending
-
-### Organization Patterns
-- **Logical Grouping**: Group related objects by business domain
-- **Consistent Prefixes**: Use company/solution prefixes consistently
-- **Module Structure**: Organize files into logical modules or folders
-
-### Extension-Specific Naming
-- **Table Extensions**: `[TableName]Ext.TableExt.al`
-- **Page Extensions**: `[PageName]Ext.PageExt.al`
-- **Clear Extension Purpose**: When extending for specific features, include context
-
-## Anti-Patterns to Avoid
-
-### Legacy/Incorrect Patterns
-```
-❌ Tab-Ext50000.CustomerExt.al          // Old NAV-style naming
-❌ TableExt50000.CustomerExt.al         // Object ID in filename
-❌ CustomerExt-50000.al                 // Mixed patterns
-❌ customer_ext.table_ext.al            // Underscore notation
-❌ CustomerExtension.TableExtension.al  // Verbose suffixes
-```
-
-### Why These Are Wrong
-- **Object IDs in Filenames**: IDs change, names are stable
-- **Abbreviated Prefixes**: "Tab-Ext" is non-standard and unclear
-- **Inconsistent Casing**: Makes files hard to locate and sort
-- **Verbose Extensions**: ".TableExtension" is unnecessarily long
-
-## Implementation Strategy
-
-### File Naming Checklist
-1. **Identify Object Name**: Use the actual AL object name from inside the file
-2. **Apply Correct Suffix**: Use standard `.ObjectType.al` pattern
-3. **Validate Consistency**: Ensure all project files follow same convention
-4. **Update References**: Check that any references or documentation align
-
-### Refactoring Existing Projects
-- **Rename Systematically**: Update all files to follow standard pattern
-- **Update Git History**: Consider preserving file history during renames
-- **Team Communication**: Ensure all team members understand new conventions
-- **Tool Configuration**: Update any build scripts or tools that reference filenames
-
-## Integration with Development Tools
-
-### VS Code Integration
-- **File Explorer Sorting**: Consistent naming improves file navigation
-- **Search and Replace**: Standard patterns make project-wide changes easier
-- **Extensions**: AL Language extension works better with standard naming
-
-### Source Control Benefits
-- **File Tracking**: Consistent naming improves change tracking
-- **Merge Conflicts**: Reduced conflicts from naming inconsistencies
-- **Review Process**: Easier code review with predictable file organization
-
+---
+title: "AL File Naming Conventions"
+domain: ["sam-coder", "roger-reviewer"]
+difficulty: "beginner"
+bc_versions: "14+"
+tags: ["file-naming", "conventions", "code-style", "organization"]
+type: "improvement-pattern"
+category: "code-organization"
+pattern_type: "good"
+severity: "high"
+impact_level: "medium"
+improvement_suggestion: "Apply consistent AL file naming conventions following alguidelines.dev standards"
+implementation_steps: ["identify-object-name", "apply-object-type-suffix", "validate-naming-pattern"]
+validation_criteria: ["consistent-naming-application", "standards-compliance"]
+technical_areas: ["al-code", "file-organization"]
+related_topics: ["al-variable-naming-conventions", "al-standard-abbreviations"]
+
+relevance_signals:
+  constructs: []
+  keywords: ["file naming", "naming convention", "TableExt", "PageExt", "Codeunit", "Table", "Page", "Report", "Query", "XMLport", "Enum", "Interface", "PermissionSet", "Pascal Case"]
+  anti_pattern_indicators: ["Tab-Ext", "Pag-Ext", "Cod50100", "object ID in filename", "underscore notation", "inconsistent casing"]
+  positive_pattern_indicators: ["ObjectName.ObjectType.al", "Pascal Case", "descriptive", "consistent prefixes", "logical grouping"]
+
+applicable_object_types: ["codeunit", "table", "tableextension", "page", "pageextension", "report", "reportextension", "query", "xmlport", "enum", "enumextension", "interface", "permissionset", "permissionsetextension", "profile", "controladdin"]
+
+relevance_threshold: 0.5
+---
+
+# AL File Naming Conventions
+
+## Overview
+
+AL file naming conventions ensure consistent project organization and improve developer experience. Following standardized patterns makes codebases more maintainable and professional.
+
+**Source**: Based on [alguidelines.dev Rule #2: File Naming Conventions](https://alguidelines.dev/docs/vibe-coding/al-naming-conventions/)
+
+**Key Principle**: File names should be descriptive and match the AL object name within the files using the pattern `<ObjectName>.<ObjectType>.al`.
+
+## Standard File Naming Pattern
+
+### Core Pattern: `<ObjectName>.<ObjectType>.al`
+
+**Table Extensions:**
+```
+✅ CORRECT: CustomerExt.TableExt.al
+✅ CORRECT: SalesHeaderExt.TableExt.al
+❌ WRONG: Tab-Ext50100.CustomerExt.al
+❌ WRONG: TableExt50100.CustomerExt.al
+```
+
+**Page Extensions:**
+```
+✅ CORRECT: CustomerCardExt.PageExt.al
+✅ CORRECT: InventorySetupExt.PageExt.al
+❌ WRONG: Pag-Ext50100.CustomerCardExt.al
+❌ WRONG: PageExt50100.CustomerCardExt.al
+```
+
+**Codeunits:**
+```
+✅ CORRECT: CustomerCommentsManager.Codeunit.al
+✅ CORRECT: PostSalesInvoice.Codeunit.al
+❌ WRONG: Cod50100.CustomerCommentsManager.al
+❌ WRONG: Codeunit50100.CustomerCommentsManager.al
+```
+
+**Event Subscribers:**
+```
+✅ CORRECT: SalesEventsSubscriber.Codeunit.al
+✅ CORRECT: CustomerEventsHandler.Codeunit.al
+```
+
+## Object Type Suffixes
+
+### Standard Suffixes
+- **Tables**: `.Table.al`
+- **Table Extensions**: `.TableExt.al`
+- **Pages**: `.Page.al`
+- **Page Extensions**: `.PageExt.al`
+- **Page Customizations**: `.PageCust.al`
+- **Reports**: `.Report.al`
+- **Report Extensions**: `.ReportExt.al`
+- **Codeunits**: `.Codeunit.al`
+- **Queries**: `.Query.al`
+- **XMLports**: `.XMLport.al`
+- **Enums**: `.Enum.al`
+- **Enum Extensions**: `.EnumExt.al`
+- **Interfaces**: `.Interface.al`
+- **Control Add-ins**: `.ControlAddin.al`
+- **Dotnet**: `.Dotnet.al`
+- **Profiles**: `.Profile.al`
+- **Permission Sets**: `.PermissionSet.al`
+- **Permission Set Extensions**: `.PermissionSetExt.al`
+
+## Best Practices
+
+### Object Name Guidelines
+- **Use Pascal Case**: CustomerCommentsManager (not customercommentsmanager)
+- **Be Descriptive**: Clearly indicate object purpose
+- **Avoid Abbreviations**: Use full words unless standard BC terms
+- **Include Context**: For extensions, indicate what you're extending
+
+### Organization Patterns
+- **Logical Grouping**: Group related objects by business domain
+- **Consistent Prefixes**: Use company/solution prefixes consistently
+- **Module Structure**: Organize files into logical modules or folders
+
+### Extension-Specific Naming
+- **Table Extensions**: `[TableName]Ext.TableExt.al`
+- **Page Extensions**: `[PageName]Ext.PageExt.al`
+- **Clear Extension Purpose**: When extending for specific features, include context
+
+## Anti-Patterns to Avoid
+
+### Legacy/Incorrect Patterns
+```
+❌ Tab-Ext50000.CustomerExt.al          // Old NAV-style naming
+❌ TableExt50000.CustomerExt.al         // Object ID in filename
+❌ CustomerExt-50000.al                 // Mixed patterns
+❌ customer_ext.table_ext.al            // Underscore notation
+❌ CustomerExtension.TableExtension.al  // Verbose suffixes
+```
+
+### Why These Are Wrong
+- **Object IDs in Filenames**: IDs change, names are stable
+- **Abbreviated Prefixes**: "Tab-Ext" is non-standard and unclear
+- **Inconsistent Casing**: Makes files hard to locate and sort
+- **Verbose Extensions**: ".TableExtension" is unnecessarily long
+
+## Implementation Strategy
+
+### File Naming Checklist
+1. **Identify Object Name**: Use the actual AL object name from inside the file
+2. **Apply Correct Suffix**: Use standard `.ObjectType.al` pattern
+3. **Validate Consistency**: Ensure all project files follow same convention
+4. **Update References**: Check that any references or documentation align
+
+### Refactoring Existing Projects
+- **Rename Systematically**: Update all files to follow standard pattern
+- **Update Git History**: Consider preserving file history during renames
+- **Team Communication**: Ensure all team members understand new conventions
+- **Tool Configuration**: Update any build scripts or tools that reference filenames
+
+## Integration with Development Tools
+
+### VS Code Integration
+- **File Explorer Sorting**: Consistent naming improves file navigation
+- **Search and Replace**: Standard patterns make project-wide changes easier
+- **Extensions**: AL Language extension works better with standard naming
+
+### Source Control Benefits
+- **File Tracking**: Consistent naming improves change tracking
+- **Merge Conflicts**: Reduced conflicts from naming inconsistencies
+- **Review Process**: Easier code review with predictable file organization
+
 *This is a foundational standard that affects all AL development. Proper file naming is the first step toward professional, maintainable Business Central extensions.*

package/embedded-knowledge/domains/taylor-docs/al-xml-documentation-structure.md

@@ -5,6 +5,16 @@ difficulty: "intermediate"
 bc_versions: "18+"
 tags: ["xml-documentation", "intellisense", "api-documentation", "object-documentation"]
 prerequisites: ["al-objects", "xml-basics"]
+
+relevance_signals:
+  constructs: ["summary", "param", "returns", "example", "remarks"]
+  keywords: ["XML documentation", "IntelliSense", "API documentation", "triple-slash", "documentation comment", "object documentation", "procedure documentation"]
+  anti_pattern_indicators: ["minimal documentation", "copy-paste descriptions", "outdated information", "excessive detail", "missing parameter info"]
+  positive_pattern_indicators: ["complete coverage", "clear language", "accurate information", "meaningful examples", "version control", "review process"]
+
+applicable_object_types: ["codeunit", "table", "page", "report", "query", "xmlport", "enum", "interface"]
+
+relevance_threshold: 0.4
 ---
 # AL XML Documentation Comment Structure for Objects
 

package/embedded-knowledge/domains/uma-ux/bc-action-shortcuts-syntax.md

@@ -1,11 +1,21 @@
----
+---
 title: "Business Central Action Shortcut Key Syntax and Implementation"
 domain: "uma-ux"
 difficulty: "intermediate"
 bc_versions: "14+"
 tags: ["shortcuts", "actions", "user-interface", "accessibility", "keyboard-navigation"]
 prerequisites: ["bc-actions", "page-design"]
----
+
+relevance_signals:
+  constructs: ["ShortcutKey", "ApplicationArea", "Promoted", "PromotedCategory", "ToolTip", "Caption"]
+  keywords: ["shortcut key", "keyboard shortcut", "action", "accessibility", "keyboard navigation", "Ctrl", "Alt", "Shift", "F-key", "modifier key"]
+  anti_pattern_indicators: ["conflicting assignments", "obscure combinations", "inconsistent patterns", "missing accessibility", "undocumented shortcuts"]
+  positive_pattern_indicators: ["intuitive mapping", "standard conventions", "conflict avoidance", "accessibility compliance", "tooltip inclusion"]
+
+applicable_object_types: ["page", "pageextension"]
+
+relevance_threshold: 0.4
+---
 # Business Central Action Shortcut Key Syntax and Implementation
 
 ## Overview