Add test coverage checklist, report template, and stack matrix for ecommerce project

- Created a test coverage checklist to ensure comprehensive testing of backend and frontend components.
- Added a test report template to standardize reporting on test execution results and gaps.
- Introduced a test stack matrix to guide the selection of testing tools and frameworks for backend and frontend.
- Established a skill for repairing failing tests, including a failure triage checklist and a test repair template.
- Documented recommended MCP stack for ecommerce development with FastAPI and React/Next.js.
- Developed a detailed README outlining the project structure, agent capabilities, and recommended workflows.
- Compiled a comprehensive workflow guide detailing step-by-step commands for project setup, testing, and SEO implementation.

site-fullstack/.github/instructions/ecommerce-ux-assets.instructions.md

@@ -0,0 +1,27 @@
+---
+name: "ecommerce-ux-assets"
+description: "Use when designing ecommerce storefronts, admin panels, mobile-first interfaces, animation systems, content imagery, or AI image prompts for an online store."
+---
+# Ecommerce UX And Asset Rules
+
+## Visual discovery
+- Ask for the brand tone, audience, price segment, market, and visual references when they are missing.
+- If the brief is vague, offer two or three distinct visual directions before implementation.
+- Avoid generic layouts. Use clear hierarchy, deliberate typography, and a defined visual mood.
+
+## Storefront UX baseline
+- Design mobile-first first, then scale up.
+- Include categories, filters, sorting, search, sticky actions where useful, and strong product detail flows.
+- Make cart, checkout, and auth feel fast and predictable.
+- Include motion with purpose: staged reveals, hover states, cart feedback, and page transitions where it improves clarity.
+
+## Admin UX baseline
+- Admin should be operationally efficient rather than decorative.
+- Use information density carefully, keep tables readable, and keep destructive actions explicit.
+- Responsive support is still required. Tablet support is mandatory, mobile support should remain workable for critical actions.
+
+## Image and content handling
+- Prefer user-provided assets or safe source material when available.
+- If final assets do not exist, generate ready-to-use prompts for an external image model.
+- Image prompts should specify subject, composition, aspect ratio, background, lighting, styling cues, and negative constraints.
+- Do not imply image rights that are not known.