feat: Implement Section component with customizable background and padding

- Added Section component with default and customizable styles.
- Created tests for Section component to validate rendering and style application.
- Introduced ShimmerLoader components for loading states.
- Implemented Google Analytics hooks for tracking page views and events.
- Added error handling hook for consistent error management.
- Created utility functions for SEO structured data generation.
- Established Zustand store for global application state management.
- Enhanced testing utilities and configurations for improved test coverage.

Author: flexdevguy

.env.example

@@ -0,0 +1,4 @@
+# Google Analytics Configuration
+# Get your Tracking ID from Google Analytics (GA4)
+# Format: G-XXXXXXXXXX
+VITE_GA_TRACKING_ID=G-XXXXXXXXXX

.eslintrc.json

@@ -0,0 +1,28 @@
+{
+  "extends": [
+    "standard",
+    "standard-with-typescript"
+  ],
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": {
+    "ecmaVersion": 2020,
+    "sourceType": "module",
+    "project": "./tsconfig.json"
+  },
+  "plugins": [
+    "react",
+    "react-hooks"
+  ],
+  "rules": {
+    "react/react-in-jsx-scope": "off",
+    "react/prop-types": "off",
+    "@typescript-eslint/explicit-function-return-type": "off",
+    "@typescript-eslint/strict-boolean-expressions": "off"
+  },
+  "env": {
+    "browser": true,
+    "es2020": true,
+    "node": true
+  }
+}
+

.github/agents.md

@@ -0,0 +1,8 @@
+# Copilot Instructions for AI Agents
+
+- Follow all workspace-specific rules and best practices.
+- Adhere to the guidelines in `.github/code guidelines.md`.
+- When generating code, prefer existing workspace patterns and utilities.
+- Reference workspace symbols and files using fully qualified links.
+- Do not generate or suggest code that violates repository policies.
+- Always check for and respect any additional instructions in the workspace.

.github/code.guidelines.md

@@ -0,0 +1,10 @@
+# Copilot Code Guidelines for Developers
+
+- Write clear, maintainable, and well-documented code.
+- Follow the formatting and linting rules defined in `.eslintrc.json`, `.prettierrc.json`, and `.standardrc.json`.
+- Use TypeScript best practices for type safety.
+- Prefer functional components and hooks in React code.
+- Organize code into appropriate domains and shared modules.
+- Write unit tests for new features and bug fixes.
+- Reference workspace symbols and files using fully qualified links.
+- Avoid introducing breaking changes without discussion.