chore: add project instructions and workflow rules to INSTRUCTIONS.md

INSTRUCTIONS.md

@@ -0,0 +1,25 @@
+# Antigravity Instructions & Project Rules
+
+This document contains critical project-specific rules for the e-tib.com codebase. Antigravity must read and follow these rules at all times.
+
+## 1. Bilingual Site (German & English) - STRICT
+- **Always update BOTH languages!** The website is bilingual. 
+- When changing content, adding pages, or updating text, you MUST always check and update both `content/de/` and `content/en/` simultaneously.
+- When adding new components with text, ensure they are built to support both languages or update the respective translation files/mechanisms. Do NOT just hardcode German text and forget the English version.
+
+## 2. No Dummy Data / No Hallucinations
+- Do not invent or hallucinate placeholder text (e.g., "Nachweis liegt vor" for certificates that don't exist). 
+- Only implement what is explicitly requested or what matches provided assets/data. 
+- If data is missing, ask the user instead of inventing placeholders.
+
+## 3. Git Workflow & RC Tagging
+- When instructed to "commit and tag" (or similar), always follow this process:
+  1. Add and commit the changes with conventional commits (`feat:`, `fix:`, `chore:`, etc.).
+  2. Check the latest tag using `git describe --tags --abbrev=0`.
+  3. Increment the RC (Release Candidate) number of the current version (e.g., if latest is `v2.2.13-rc19`, the new tag is `v2.2.13-rc20`).
+  4. Create the tag: `git tag vX.Y.Z-rcN`.
+  5. Push the commit and the tag: `git push origin main --tags`.
+
+## 4. Work Exclusively on the Correct Branch
+- Follow the `USER_GLOBAL` directive: If on `main`, create a branch unless explicitly told to work on `main`. 
+- For e-tib.com, often small fixes are done on `main` if the user commands it ("auf main arbeiten"), but always verify context.