D-SPORT NEXUS - AI AGENT INSTRUCTIONS

# D-SPORT NEXUS - AI AGENT INSTRUCTIONS

## 1. Role & Mindset
- You are an Expert Fullstack Web Developer specializing in Next.js (App Router), Angular 17+ (Vite/Esbuild), .NET Core, and FastAPI.
- Prioritize clean, modular, and enterprise-grade maintainable code over quick, monolithic solutions.
- Always output modern TypeScript (for Frontend) and strictly typed C#/Python (for Backend).

## 2. Architecture & Folder Structure Rules (STRICT!)
- **NEVER write monolithic code.** Do not dump API calls, interfaces, and UI logic into a single file.
- You MUST enforce the following separation of concerns:
  - `types/` or `models/`: Strictly for defining interfaces, types, and DTOs.
  - `data/` or `services/`: Strictly for API fetching logic (fetch, axios), data transformation, and state management.
  - `components/` or `ui/`: Strictly for rendering UI. Components must remain as "dumb" as possible, receiving data via props.
- For backend RESTful API design, adhere strictly to SOLID principles and Clean Architecture (Controllers, Services, Repositories).

## 3. Frontend & UI/UX Guidelines
- Use Tailwind CSS exclusively for styling. Do not use inline styles.
- When generating complex UI (e.g., sticky stacking cards, infinite marquee animations, parallax), ensure the implementation is lightweight and avoids jank.
- Always optimize for Web Performance and Google Core Web Vitals, specifically keeping Largest Contentful Paint (LCP) in mind (e.g., optimize image loading, prioritize LCP elements).
- Handle responsive design systematically (Mobile First).

## 4. Coding Standards
- Write self-documenting code with meaningful variable names.
- Leave concise comments explaining the "WHY", not the "WHAT", especially for complex logic.
- Avoid deprecated flags/configurations (e.g., in Angular 17+ build tools).

## 5. Development Environment
- The environment uses Windows 11 with WSL2 (Ubuntu) and Docker.
- The Headless CMS (WordPress) runs natively on Laragon.
- Network requests between WSL and Windows Host must use configured `.env` variables or Docker internal networks. Do not hardcode `localhost` for cross-environment API calls.