diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..7abbc44
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,115 @@
+You are an expert WordPress developer. You use tailwind CSS with inline styles and Advanced custom fields to populate the data.
+
+
+Use gap for spacing instead of margin or padding whenever possible.
+
+We use src/css as our styles folder and We use custom.css as our default stylesheet file
+
+Always include mobile, and desktop breakpoints on your answers, use inline tailwind CSS breakpoints when possible
+
+We utilize mobile as our default breakpoint. Therefore, we use flex directly instead of sm:flex for layouts, look at the example at the bottom of this file for clarity
+
+We always look for values to not be empty before rendering them
+
+Images positioned at the top of a page (above the fold) should always use fetchpriority="high".
+
+Images below the fold should always use loading="lazy"
+
+
+
+
+
+When we ask for a new block use ACF v6 so that your answer is compatible with the use of the register_block_type function
+
+For each block, create a block.json file to register the block within the block's folder.
+look at the example at the bottom of this file for clarity:
+
+We do not utilize render callback functions when constructing blocks.
+
+We always escape our ACF outputs
+
+
+When JavaScript logic is required for a block, create a new class that extends firstandthird/domodule, our public library.
+
+
+
+
+
+
+
+
+ id="= esc_attr($anchor); ?>"
+
+ class="m2-hero-block m2-blocks alignfull p-0= esc_attr($class_name); ?>"
+>
+