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,20 @@
+# SEO Implementation Checklist
+
+Before changing code, confirm the current project has or needs:
+
+- Metadata generation by page type.
+- Canonical tags and noindex controls.
+- XML sitemap generation.
+- robots.txt policy.
+- Open Graph and social metadata.
+- Structured data by page type.
+- Breadcrumb markup and UI breadcrumbs.
+- Internal linking modules.
+- Category intro content or SEO content blocks.
+- Product content sections such as FAQs, specs, care, compatibility, or shipping info.
+- Search result and filter route indexation rules.
+- Pagination or infinite-scroll SEO handling.
+- Image component support for alt text, size hints, and optimized delivery.
+- Performance-sensitive rendering for money pages.
+
+If any item is missing, decide whether to implement it now, defer it, or document it as blocked by architecture.
@@ -0,0 +1,31 @@
+# Page Type SEO Matrix
+
+## Homepage
+- Brand-level title and description.
+- Organization and WebSite schema.
+- Clear links to priority categories and collections.
+
+## Category and collection pages
+- Unique title, meta description, H1, and intro copy strategy.
+- Breadcrumbs.
+- ItemList schema when appropriate.
+- Canonical rules for filters and sort states.
+- Internal links to related categories and featured products.
+
+## Brand pages
+- Brand-specific copy and linked collections.
+- Canonical protection against overlap with categories or collections.
+
+## Product pages
+- Product schema with real offer data.
+- Rich metadata with variant-aware handling.
+- FAQ or support content blocks when relevant.
+- Internal links to related products and parent categories.
+
+## Editorial or guide pages
+- Article schema when relevant.
+- Strong internal links into commercial pages.
+- Intent-aligned headings and content sections.
+
+## Utility pages
+- Cart, account, checkout, login, internal search, and thin utilities should usually be noindex.
@@ -0,0 +1,29 @@
+# Technical Execution Map
+
+## Metadata layer
+- Define where titles, descriptions, canonicals, Open Graph, and robots directives are generated.
+- Prefer centralized page-type SEO configuration over scattered hardcoded tags.
+
+## Routing and index control
+- Ensure low-value routes can emit noindex or canonical rules.
+- Align filtered routes, sorted routes, search routes, and pagination with the SEO policy.
+
+## Structured data layer
+- Use JSON-LD generated from real page data.
+- Keep schema close to the page data source to reduce drift.
+
+## Sitemap and robots
+- Generate sitemaps only for valuable indexable URLs.
+- Exclude duplicates, noindex pages, and thin utility pages.
+
+## Internal linking systems
+- Breadcrumbs, related content blocks, category cross-links, product recommendations, and editorial links should be intentional and reusable.
+
+## Performance-sensitive work
+- Protect LCP, INP, and CLS while adding SEO features.
+- Avoid heavy client-only SEO logic for key landing pages.
+
+## Validation
+- Check for duplicate titles or duplicate canonicals.
+- Check that schema matches visible content.
+- Check that robots and sitemap policy are coherent.