What problem does it solve?
Standard LD+JSON recipe parsing fails for vendor sites that require custom DOM parsing, branded ingredient enforcement, or bespoke data migration configuration, creating gaps in recipe data ingestion for the Pear Commerce platform.
Core Features & Use Cases
- Custom DOM Parser Implementation: Build site-specific recipe parsers using stable selectors for recipe headers, hero images, and ingredient sections instead of relying on generic theme wrappers.
- Branded Ingredient Handling: Preserve vendor branding in ingredient text by appending vendor names to product-linked ingredients that lack explicit branding.
- Idempotent Migration & Test Coverage: Add non-duplicate VendorRecipeIngestor database configurations and targeted test coverage for custom parser logic to ensure reliable integration.
- Use Case: For a grocery vendor's recipe site that uses custom HTML markup instead of LD+JSON, use this skill to build a dedicated parser, enforce branded ingredient labels, and add migration and test coverage to integrate it into the Pear recipe ingestion pipeline.
Quick Start
Use the vendor-recipe-ingestor skill to implement a custom DOM parser, branded ingredient customizer, idempotent data migration, and targeted tests for a vendor recipe site that requires bespoke ingestion beyond standard LD+JSON support.