What problem does it solve? Adding site-specific product extraction to a Chrome extension requires checking each site's terms of use, recording compliance decisions, building extraction candidates, and verifying them against saved pages and real-extension E2E tests. This Skill orchestrates that entire workflow safely, ensuring no page content, product values, or credentials leak into the repository or decision records. ## Core Features & Use Cases - Terms-of-use gating: Explores the target site's official terms before any work, records findings in a decision log, and stops only on explicit prohibitions rather than ambiguity. - Isolated work units: Creates timestamped, Git-ignored work units under /.site-extraction-work/ with separate decision, candidate, and verification records, never overwriting prior runs. - Staged candidate validation: Builds extraction candidates restricted to existing categories and attribute keys, verifies them against saved page material, then hands off to real-extension E2E and pnpm validate before proposing registration. - Use Case: A developer wants to add extraction support for a new PC parts retailer. Provide the representative product page URL, and the Skill records the terms review, drafts selectors for allowed fields, verifies them, and proposes a registration diff only after all checks pass. ## Quick Start Start site-specific extraction authoring for the product page at this representative URL and record the terms-of-use review before creating any candidates.
