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:
ВяткинАртём
@@ -0,0 +1,13 @@
|
||||
name: "Ecommerce Build From Brief"
|
||||
description: "Build an ecommerce project from .ai/STORE-BRIEF.md, creating AGENTS.md first and then implementing backend, storefront, and admin scope."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Build the project from the normalized brief.
|
||||
|
||||
Requirements for this run:
|
||||
- Read .ai/STORE-BRIEF.md first.
|
||||
- If .ai/STORE-BRIEF.md is missing, create it first or ask to run the brief-preparation workflow.
|
||||
- Create or update AGENTS.md before application code.
|
||||
- Before serious backend or frontend edits, create a timestamped snapshot in .backup/ and do not modify older backup entries.
|
||||
- Build with a scalable architecture where models, services, config, routing, components, features, and api layers live in their own folders.
|
||||
- Implement backend, storefront, and admin panel or back office according to the brief.
|
||||
- Preserve mobile-first UX, animation quality, and asset handling.
|
||||
@@ -0,0 +1,12 @@
|
||||
name: "Ecommerce Code Review"
|
||||
description: "Run a strict full-project code review using pyproject, package.json, and current versions to produce .ai/CODE-REVIEW.md with harsh findings and fixes."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Review the project strictly.
|
||||
|
||||
Requirements for this run:
|
||||
- Inspect the actual project configuration first.
|
||||
- Respect configured Python quality tools such as mypy, ty, ruff, and deptry.
|
||||
- Review React code for readability, maintainability, and appropriate use of modern supported features.
|
||||
- Prefer findings over praise.
|
||||
- Create or update .ai/CODE-REVIEW.md.
|
||||
- Use current, version-appropriate guidance rather than outdated generic advice.
|
||||
@@ -0,0 +1,14 @@
|
||||
name: "Ecommerce Extend Existing"
|
||||
description: "Extend an existing ecommerce codebase with new storefront, backend, admin panel, AGENTS.md, or UX work while preserving the current architecture."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Extend the existing ecommerce project.
|
||||
|
||||
Requirements for this run:
|
||||
- Inspect the current architecture before proposing structural changes.
|
||||
- Create or update AGENTS.md before substantial implementation if the repo does not already define the working rules.
|
||||
- Before serious backend or frontend edits, create a timestamped snapshot in .backup/ and do not modify older backup entries.
|
||||
- Keep backend and frontend responsibilities in dedicated folders and improve weak architecture instead of extending a messy flat structure.
|
||||
- Preserve existing conventions when they are sound.
|
||||
- Add or improve storefront, backend, admin panel, data model, filters, sorting, auth, or content management as needed.
|
||||
- Keep mobile behavior, animation quality, and operational admin UX in scope.
|
||||
- Where assets are missing, prepare source requests or generation prompts instead of leaving the project visually blocked.
|
||||
@@ -0,0 +1,21 @@
|
||||
name: "Ecommerce From Zero"
|
||||
description: "Create a new ecommerce project from scratch with FastAPI, React, storefront, admin panel, AGENTS.md, and modern mobile-first UX."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Create a new ecommerce project from scratch.
|
||||
|
||||
Requirements for this run:
|
||||
- Ask only the minimum blocking questions.
|
||||
- First normalize the request into .ai/STORE-BRIEF.md.
|
||||
- Use .ai/STORE-BRIEF.md as the single source of truth for implementation.
|
||||
- Decide monorepo versus split repos with the user if it is not already explicit.
|
||||
- Create or update AGENTS.md before application code.
|
||||
- If the repo already contains backend or frontend code that will be heavily changed, create a timestamped snapshot in .backup/ before editing it.
|
||||
- Use a large-project architecture with dedicated folders for backend layers and frontend layers instead of a flat structure.
|
||||
- Default to FastAPI plus PostgreSQL on the backend.
|
||||
- Default to React plus Next.js on the frontend.
|
||||
- Include storefront and admin panel or back office unless the user explicitly excludes one of them.
|
||||
- Cover home, catalog, categories, filters, sorting, product detail, cart, auth, and other required commerce pages.
|
||||
- Support an account area when needed.
|
||||
- If the project should work without customer accounts, choose and justify localStorage or cookie or server-backed cart behavior.
|
||||
- Build a modern 2026-level, mobile-first UI with purposeful animation.
|
||||
- If final visual assets are missing, source references or generate external image prompts.
|
||||
@@ -0,0 +1,11 @@
|
||||
name: "Ecommerce Prepare Brief"
|
||||
description: "Turn a rough ecommerce request into .ai/STORE-BRIEF.md by asking focused questions and normalizing the project scope before code generation."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Prepare the project for implementation.
|
||||
|
||||
Requirements for this run:
|
||||
- Do not start application scaffolding yet.
|
||||
- Ask only the minimum high-impact questions.
|
||||
- Create or update .ai/STORE-BRIEF.md.
|
||||
- Normalize the user request into a build-ready markdown brief for storefront, backend, admin panel, integrations, design, and AGENTS.md planning.
|
||||
- If the project is split across repos, make the current repo responsibilities explicit.
|
||||
@@ -0,0 +1,12 @@
|
||||
name: "Ecommerce SEO Implementation"
|
||||
description: "Implement SEO changes directly in an ecommerce codebase from .ai/SEO-PLAN.md or .ai/STORE-BRIEF.md."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Implement SEO changes in the project.
|
||||
|
||||
Requirements for this run:
|
||||
- Read .ai/SEO-PLAN.md first if it exists.
|
||||
- If .ai/SEO-PLAN.md is missing, use .ai/STORE-BRIEF.md or ask to prepare the SEO strategy first.
|
||||
- Before serious backend or frontend edits, create a timestamped snapshot in .backup/ and do not touch older backup entries.
|
||||
- Apply SEO in code, not just recommendations.
|
||||
- Cover metadata, schema, canonicals, robots, sitemap, internal linking, page-template SEO behavior, and indexation rules as appropriate for the codebase.
|
||||
- Report what was implemented and what remains blocked or deferred.
|
||||
@@ -0,0 +1,12 @@
|
||||
name: "Ecommerce SEO Review"
|
||||
description: "Audit implemented ecommerce SEO and write a structured .ai/SEO-REVIEW.md with prioritized findings and fixes."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Review the current ecommerce project's SEO implementation.
|
||||
|
||||
Requirements for this run:
|
||||
- Read .ai/SEO-PLAN.md first if it exists.
|
||||
- Review the codebase, not just the plan.
|
||||
- Create or update .ai/SEO-REVIEW.md.
|
||||
- Prioritize findings by severity.
|
||||
- Separate confirmed issues from assumptions and runtime-only unknowns.
|
||||
- End with a practical remediation plan.
|
||||
@@ -0,0 +1,10 @@
|
||||
name: "Ecommerce SEO Strategy"
|
||||
description: "Create or improve an ecommerce SEO strategy across technical SEO, content architecture, schema, metadata, internal linking, and measurement."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Plan or improve SEO for the ecommerce project.
|
||||
|
||||
Requirements for this run:
|
||||
- Read .ai/STORE-BRIEF.md first if it exists.
|
||||
- If the task is broad, create or update .ai/SEO-PLAN.md.
|
||||
- Cover technical SEO, information architecture, category strategy, product page SEO, metadata, schema markup, internal linking, content gaps, and measurement.
|
||||
- Do not promise guaranteed first-place rankings; optimize for the strongest realistic organic foundation.
|
||||
@@ -0,0 +1,12 @@
|
||||
name: "Ecommerce Test Implementation"
|
||||
description: "Write backend and frontend automated tests, run them, and create .ai/TEST-REPORT.md with results and gaps."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Create or extend automated tests for the project.
|
||||
|
||||
Requirements for this run:
|
||||
- Inspect the current backend and frontend test stack first.
|
||||
- Add meaningful backend and frontend tests for the relevant flows.
|
||||
- Before serious backend or frontend edits, create a timestamped snapshot in .backup/ and keep older backup entries immutable.
|
||||
- Run the relevant test suites.
|
||||
- Create or update .ai/TEST-REPORT.md.
|
||||
- If failures remain, clearly say that the next step is to run Ecommerce Test Repair.
|
||||
@@ -0,0 +1,13 @@
|
||||
name: "Ecommerce Test Repair"
|
||||
description: "Fix failing backend and frontend tests, rerun them, and write .ai/TEST-REPAIR.md with results and blockers."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
Repair the current test failures.
|
||||
|
||||
Requirements for this run:
|
||||
- Read .ai/TEST-REPORT.md first if it exists.
|
||||
- Inspect actual failing test output before making changes.
|
||||
- Before serious backend or frontend edits, create a timestamped snapshot in .backup/ and do not modify older backup entries.
|
||||
- Fix the underlying code or the tests depending on root cause.
|
||||
- Rerun the affected suites.
|
||||
- Create or update .ai/TEST-REPAIR.md.
|
||||
- Do not weaken tests just to make them pass.
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
name: "Ecommerce Visual Pack"
|
||||
description: "Produce a visual direction, asset plan, and AI image prompts for an ecommerce storefront and admin experience."
|
||||
agent: "shop-fullstack-fastapi-react"
|
||||
---
|
||||
Prepare the visual system for an ecommerce project.
|
||||
|
||||
Requirements for this run:
|
||||
- Ask for missing brand and audience information only when necessary.
|
||||
- Produce a concise visual direction for storefront and admin.
|
||||
- Define typography, color logic, layout rhythm, motion cues, and content block style.
|
||||
- List required assets for hero, categories, product placeholders, banners, social preview, and empty states.
|
||||
- If real assets are unavailable, generate strong prompts that the user can send to an external image model.
|
||||
Reference in New Issue
Block a user