ВяткинАртём
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.
44 lines
1.6 KiB
Markdown
44 lines
1.6 KiB
Markdown
# Discovery Question Bank
|
|
|
|
Ask only the questions that materially change implementation. Prefer short batches.
|
|
|
|
## Product and business
|
|
- What does the store sell and to whom.
|
|
- Is this B2C, B2B, or mixed.
|
|
- What market or country is the primary target.
|
|
|
|
## Repository and delivery mode
|
|
- Is the target a monorepo or split repos.
|
|
- If split repos, which repo is being worked on now.
|
|
|
|
## Storefront scope
|
|
- Which pages are mandatory at launch.
|
|
- Is customer auth required, optional, or excluded.
|
|
- Is checkout needed, or is the target lead capture or quote request.
|
|
- Should there be wishlist, favorites, recently viewed, reviews, blog, or CMS pages.
|
|
|
|
## Cart and order model
|
|
- Is guest cart required.
|
|
- Should the cart persist across devices.
|
|
- Are pricing, promos, or SSR constraints strong enough to require cookie or server-backed cart.
|
|
|
|
## Admin and operations
|
|
- Which admin modules are mandatory: catalog, orders, users, content, promos, settings, dashboards, roles.
|
|
- Which staff roles are needed.
|
|
- Are audit logs, bulk actions, import or export flows required.
|
|
|
|
## Catalog and data
|
|
- Which entities exist: categories, brands, collections, attributes, variants, bundles.
|
|
- Are stock tracking, preorder, backorder, or dynamic pricing needed.
|
|
|
|
## Integrations
|
|
- Payments, delivery, CRM, ERP, analytics, email, storage, search.
|
|
|
|
## Design and assets
|
|
- What visual direction, brand tone, and references exist.
|
|
- Are production-ready assets available.
|
|
- If not, should external image-generation prompts be prepared.
|
|
|
|
## Technical constraints
|
|
- Preferred frontend stack if different from Next.js.
|
|
- Localization, SEO, multi-currency, or compliance requirements. |