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.
2026-05-20 18:09:24 +03:00
parent 5699670ea0
commit 2817cf8dc6
96 changed files with 2987 additions and 2888 deletions
@@ -0,0 +1,12 @@
+# Discovery Checklist
+
+- What does the store sell and in which market.
+- Is the delivery mode monorepo or split repos.
+- Does the storefront need customer accounts, guest checkout, or both.
+- Should anonymous carts live in localStorage, cookies, or server state.
+- Which admin roles are required.
+- Which catalog entities exist: categories, brands, attributes, variants, collections, bundles.
+- Which business flows matter: promos, delivery, pickup, preorder, lead capture, or full checkout.
+- Which external services are needed: payment, CRM, ERP, email, analytics, search, storage.
+- Which visual direction fits the brand and audience.
+- Which content and images already exist and which must be generated.
@@ -0,0 +1,17 @@
+# Image Prompt Template
+
+Use this template when the project needs visuals but the final assets do not exist yet.
+
+Prompt structure:
+- Brand and market context
+- Exact subject
+- Composition and camera distance
+- Aspect ratio and framing
+- Background and props
+- Lighting and mood
+- Material, texture, and styling details
+- Output quality cues
+- Negative constraints
+
+Example skeleton:
+Create a premium ecommerce hero image for a {brand type} store selling {product type}. Show {subject} in a {composition} composition, shot for a {aspect ratio} canvas. Use a {background style} background with {lighting style} lighting. Visual tone: {keywords}. Include room for headline text. Avoid watermarks, distorted hands, broken anatomy, cluttered backgrounds, oversaturated colors, and unreadable product details.
@@ -0,0 +1,30 @@
+# AGENTS.md Template For Monorepo
+
+## Product scope
+- Store type and target audience.
+- Required storefront pages and business flows.
+- Required admin or back office flows.
+
+## Repository structure
+- Root folders, package manager, environments, and local run commands.
+- Frontend and backend ownership boundaries.
+- Shared schema or contract locations.
+
+## Backend rules
+- FastAPI service boundaries.
+- Database stack, migrations, auth, and role model.
+- API naming and validation conventions.
+
+## Frontend rules
+- React framework choice.
+- Routing, layout structure, UI architecture, and data fetching strategy.
+- Responsive, accessibility, and animation expectations.
+
+## Admin rules
+- Admin modules, roles, dashboards, audit-sensitive actions, and content workflows.
+
+## Assets and content
+- Source asset folders, placeholder strategy, and external image prompt workflow.
+
+## Delivery rules
+- Definition of done, testing expectations, and how to handle missing requirements.
@@ -0,0 +1,20 @@
+# AGENTS.md Template For Split Backend Repo
+
+## Repo role
+- This repo owns FastAPI services, database models, auth, admin APIs, and integrations.
+- It serves the storefront and admin frontend repo through explicit contracts.
+
+## Backend scope
+- Catalog, taxonomy, auth, customers, carts, orders, content, settings, and admin operations.
+- Migrations, background jobs, storage, and integration boundaries.
+
+## Contract rules
+- Keep OpenAPI and schema naming stable.
+- Document any breaking change for the frontend repo before implementation.
+
+## Security and roles
+- Separate customer and staff permissions.
+- Apply RBAC for admin operations.
+
+## Delivery rules
+- Maintain migration safety and predictable local development.
@@ -0,0 +1,20 @@
+# AGENTS.md Template For Split Frontend Repo
+
+## Repo role
+- This repo owns the storefront and admin UI surface.
+- It consumes backend contracts from the paired backend repo.
+
+## Frontend scope
+- Storefront routes, account routes when needed, and admin routes or admin app.
+- Design system, responsive rules, motion rules, and accessibility baseline.
+
+## Data contract rules
+- Do not invent backend fields without documenting the contract.
+- Keep request and response assumptions aligned with the backend repo.
+
+## Asset workflow
+- Define source imagery, placeholder policy, and external generation prompt policy.
+
+## Delivery rules
+- Keep mobile storefront quality high.
+- Keep admin workflows efficient and reliable.