ВяткинАртём
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.
3.6 KiB
3.6 KiB
name, description, argument-hint
| name | description | argument-hint |
|---|---|---|
| ecommerce-seo-implementation | Implement SEO directly in an ecommerce codebase. Use for applying .ai/SEO-PLAN.md in code: metadata, schema markup, canonicals, sitemap, robots, internal linking, page templates, and crawl or index rules. | Describe whether to apply the full SEO plan or only specific SEO areas such as metadata, schema, category SEO, or technical SEO |
Ecommerce SEO Implementation
When to use
- Applying an existing .ai/SEO-PLAN.md to a real ecommerce codebase.
- Implementing SEO directly in frontend, backend, routing, templates, schema, metadata, and technical platform behavior.
- Converting SEO recommendations into production-ready code and content structure.
Goal
- Execute SEO changes in code, not just describe them.
- Use .ai/SEO-PLAN.md as the source of truth when it exists.
- If .ai/SEO-PLAN.md is missing, derive the minimum required context from .ai/STORE-BRIEF.md or ask to prepare the SEO strategy first.
Preconditions
- Prefer having .ai/SEO-PLAN.md.
- If .ai/SEO-PLAN.md is absent but the user explicitly wants implementation now, create a compact implementation assumption set from .ai/STORE-BRIEF.md and state the risk.
Required workflow
- Read .ai/SEO-PLAN.md first when it exists.
- Read .ai/STORE-BRIEF.md and AGENTS.md if they exist to align implementation with the product scope and repo rules.
- Before serious backend or frontend edits, create a timestamped snapshot under .backup/ and keep that folder append-only.
- Audit the current codebase against implementation checklist.
- Map required changes by page type using page type SEO matrix.
- Implement technical SEO behavior using technical execution map.
- Apply metadata, canonicals, robots policy, sitemap generation, schema markup, internal linking, and template-level SEO content where appropriate.
- Validate that SEO changes do not create index bloat, duplicate pages, or structured data inconsistencies.
- Report what was implemented, what remains manual, and what should be measured after deployment.
What this skill should implement
- Metadata systems for homepage, category, collection, brand, product, article, and utility pages.
- Canonical and noindex rules for filters, sort states, pagination, search results, cart, account, and utility routes.
- XML sitemap generation and robots policy.
- Structured data for organization, website, breadcrumbs, item lists, products, articles, FAQs, and local business when applicable.
- Breadcrumbs and internal linking modules.
- Category and product template support for SEO copy, FAQs, and content blocks when the architecture allows it.
- Image SEO basics: alt text support, responsive image behavior, and index-safe media handling.
- Performance-sensitive SEO work where it is practical within the current codebase.
Constraints
- Do not generate spammy or keyword-stuffed copy.
- Do not index low-value filter combinations by default.
- Do not implement fake ratings, fake reviews, or misleading schema.
- Do not add SEO code that conflicts with the project routing or rendering model.
Outputs
- Implemented code changes in the project.
- Optional update to .ai/SEO-PLAN.md when implementation assumptions change.
- Clear summary of completed SEO work, remaining gaps, and validation steps.