ВяткинАртём
2817cf8dc6
- 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.
14 lines
1.1 KiB
Markdown
14 lines
1.1 KiB
Markdown
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. |