ВяткинАртём
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.
2.0 KiB
2.0 KiB
name, description, argument-hint
| name | description | argument-hint |
|---|---|---|
| ecommerce-brief-preparation | Turn a rough ecommerce request into a normalized implementation brief. Use for clarifying requirements, asking targeted questions, and creating .ai/STORE-BRIEF.md before code generation. | Describe the store idea, constraints, and anything you already know |
Ecommerce Brief Preparation
When to use
- Starting a new ecommerce project from a rough or incomplete idea.
- Normalizing a user request before scaffolding code.
- Creating a single source of truth for storefront, backend, admin panel, and design decisions.
Goal
- Ask only the high-impact questions that unblock architecture, UX, catalog, auth, cart, admin, integrations, and visual direction.
- Convert the user's request into a structured file named .ai/STORE-BRIEF.md based on STORE-BRIEF.md.
- Record explicit decisions, assumptions, and unresolved risks.
Required workflow
- Parse the initial user request.
- Use discovery question bank to ask only the questions that materially affect implementation.
- Decide whether the target is monorepo or split repos.
- Normalize the result into .ai/STORE-BRIEF.md.
- If the project is split across repos, create a repo-local .ai/STORE-BRIEF.md for the current repo and document the counterpart repo responsibilities.
- Do not scaffold application code in this step unless the user explicitly asks for both steps in one run.
Output requirements for .ai/STORE-BRIEF.md
- Project summary and business context.
- Repo mode and delivery assumptions.
- Storefront scope.
- Admin panel or back office scope.
- Auth and cart decisions.
- Data model outline.
- Integrations.
- Visual direction and asset status.
- Development questions answered.
- Assumptions and open risks.
- AGENTS.md creation plan.
- Implementation phases for the build step.