retailer-production-integration

Convert retailer feasibility plans into production integration code for Pear's platform.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill retailer-production-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retailer-production-integration
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/retailer-production-integration
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill retailer-production-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the gap between temporary retailer feasibility work and production-ready integration code, ensuring teams do not leave unmaintained plan files in the codebase and follow Pear's engineering standards for live retailer integrations.

Core Features & Use Cases

  • End-to-End Production Workflow: Guides implementation of all required production classes including ItemIdInfoResolver, UPCRetailerZipAvailabilityRecomputer, BatchAvailabilityUpdater, and idempotent RetailPartner setup migrations.
  • Engineering Standard Enforcement: Embeds Pear's requirements for Spring service injection, proxy-backed live routes, UPC validation rules, and pre-PR review checklists to avoid common integration pitfalls.
  • Use Case: After a feasibility plan proves a new retailer's UPC resolution and availability routes work, use this skill to implement the production integration, add required @Script tests, and delete the temporary feasibility plan files before opening a PR.

Quick Start

Use the retailer-production-integration skill to implement production retailer integration classes from a proven feasibility plan, following the provided workflow to create resolvers, availability updaters, migrations, and production tests before submitting a PR.

Frequently Asked Questions about retailer-production-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a retailer feasibility plan into production Spring service code?

To convert retailer feasibility plans into production Spring service code, implement required classes like ItemIdInfoResolver and BatchAvailabilityUpdater, enforce Spring injection, add idempotent migrations, and run pre-PR checklists.

What production classes are required for a new retailer integration?

Required production classes for retailer integration include ItemIdInfoResolver, UPCRetailerZipAvailabilityRecomputer, BatchAvailabilityUpdater, and idempotent RetailPartner setup migrations following Pear's engineering standards.

How do I set up idempotent data migrations for a retail partner integration?

Set up idempotent data migrations by creating RetailPartner setup migrations that follow Pear's engineering standards, ensuring proxy-backed live routes and UPC validation rules are enforced before opening a pull request.

Do I need proxy-backed live routes for production retailer availability updates?

Yes, proxy-backed live routes are required for production retailer availability updates. The integration enforces this alongside Spring service injection and UPC validation rules to ensure production-grade retailer routes.

When should I delete temporary feasibility plan files during retailer integration?

Delete temporary feasibility plan files after implementing the production integration classes, adding required @Script tests, and verifying the workflow is complete, ensuring no unmaintained plan files remain before opening a PR.

What's the best way to prepare a retailer integration PR for production review?

The best way to prepare a retailer integration PR is to complete a pre-PR review checklist, verify Spring service injection, confirm idempotent migrations, and ensure all @Script tests pass before submission.