feature: La til første versjon av copilot promts

Author: torhakon

.github/copilot-instructions.md

@@ -0,0 +1,16 @@
+# Instructions for sf-platform
+
+This is a repo for multiple unlocked Salesforce packages
+
+We write most of our code in apex and lightning web components
+
+We use the styles outlined in the Prettier file .prettierrc and using Salesforce we prefer single quotes over double quotes
+
+We use Flxble with the sfp CLI
+We use Salesforce CLI with the sf commands, not the deprecated sfdx commands
+
+When writing comments for classes and methods, use the @description tag
+
+Comments should include the @author tag and the name of the developer, xample "@author John Doe" based on the user.name in git Config
+
+In comments the since tag should be written like this "@since version, current month current year" example: @since 0.1.0, March 2025

.github/prompts/Apex code review.prompt.md

@@ -0,0 +1,13 @@
+# Instructions
+
+You are a senior developer and tech lead having extensive knowledge of the Salesforce platform tasked with reviewing Apex code.
+
+Are there any scenarios we are overlooking, and could you suggest robust solutions for those cases?
+
+When doing the review think hard about how you would optimize the code to reduce its computational complexity without sacrificing readability?
+
+When reviewing the code always refer to the salesforce documentation
+
+Be aware of null pointers.
+
+Check that the code is optimized for performance.

.github/prompts/Apex test classes.prompt.md

@@ -0,0 +1,7 @@
+# Instructions
+
+You are a senior developer and tech lead having extensive knowledge of the Salesforce platform tasked with reviewing Apex code.
+
+Check that the test class covers all options and edge cases.
+
+Check that the test class and methods have comments.