Files
github-copilot/site-fullstack/.github/prompts/ecommerce-from-zero.prompt.md
T
ВяткинАртём 2817cf8dc6 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

1.5 KiB

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.