Add CMFRT naming conventions, object ID ranges, and patterns documentation

- Introduced guidelines for using the "CMFRT" prefix in object names, fields, and procedures to avoid naming collisions and ensure clarity.
- Established rules for object ID ranges to prevent conflicts with other extensions and maintain historical integrity.
- Documented best practices and anti-patterns for various coding patterns, including case statements, interface injection, label usage, and validation methods.
- Implemented a standards review skill to evaluate AL source changes against CMFRT company standards, ensuring compliance with naming, permissions, and architectural patterns.

custom/knowledge/naming/cmfrt-object-id-ranges.good.al

@@ -0,0 +1,24 @@
+// Product extension — IDs are within the product range 2045081..2046580.
+table 2045081 "CMFRT GD POI"
+{
+    Caption = 'POI';
+    DataClassification = CustomerContent;
+
+    fields
+    {
+        field(2045081; "Code"; Code[20]) { DataClassification = CustomerContent; }
+        field(2045082; "Description"; Text[100]) { DataClassification = CustomerContent; }
+    }
+}
+
+// Customer extension — IDs are within the customer range 55000..55999.
+table 55000 "CMFRT JO Customer Site"
+{
+    Caption = 'Customer Site';
+    DataClassification = CustomerContent;
+
+    fields
+    {
+        field(55000; "Code"; Code[20]) { DataClassification = CustomerContent; }
+    }
+}