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.
This commit is contained in:
ВяткинАртём
2026-05-20 18:09:24 +03:00
parent 5699670ea0
commit 2817cf8dc6
96 changed files with 2987 additions and 2888 deletions
@@ -0,0 +1,27 @@
# Keyword Intent Framework
## Intent buckets
- Transactional: buy-now, price, delivery, in-stock, order intent.
- Commercial investigation: best, compare, review, top, versus, alternatives.
- Informational: how to choose, how to use, care guides, ingredient guides, compatibility guides.
- Navigational and brand: brand, collection, store name, product line, branded queries.
## Mapping rules
- Homepage should target broad category and brand-level demand, not all keywords.
- Category and subcategory pages should target the highest-volume commercial and transactional themes.
- Product pages should target explicit product, variant, model, SKU, brand, and long-tail modifiers.
- Guide and FAQ pages should support commercial pages and capture informational demand.
## Output fields
- Keyword theme
- Primary intent
- Suggested landing page type
- Funnel stage
- Priority
- Required content blocks
- Internal link targets
## Ecommerce caution points
- Do not create indexable pages for every low-value filter combination.
- Avoid cannibalization between category pages, collection pages, and blog content.
- Prefer strong category and brand hubs over thin near-duplicate pages.