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/patterns/cmfrt-use-confirmmanagement.good.al

@@ -0,0 +1,15 @@
+codeunit 2045750 "CMFRT GD Deletion Handler"
+{
+    procedure CMFRTGDDeletePOI(POICode: Code[20])
+    var
+        CMFRTGDPOI: Record "CMFRT GD POI";
+        ConfirmManagement: Codeunit "Confirm Management";
+        DeleteConfirmQst: Label 'Delete POI %1?', Comment = '%1 = POI Code';
+    begin
+        if not ConfirmManagement.GetResponseOrDefault(StrSubstNo(DeleteConfirmQst, POICode), false) then
+            exit;
+
+        if CMFRTGDPOI.Get(POICode) then
+            CMFRTGDPOI.Delete(true);
+    end;
+}