Claude Code plugin: marketplace-agnostic purchasing and procurement process — spec definition from a vague want or a photograph, annotated search vocabulary, intake, research, compare, evaluate, recommend, market-check, spec-driven market landscape surveys, live price/delivery scanning through your own VPN egress…
Interviews the user about their tastes, parses ingested history (OPML, watch history, reading lists), and maintains memory/preferences.md as the canonical preference profile.
Compares prices across vendors and markets, calculates markups, and factors in import costs (shipping, VAT, customs). Use when evaluating value across multiple sources or when deciding buy-local vs. import.
Extracts structured product data (name, brand, price, SKU, vendor) from screenshots, PDFs, and catalog images. Use when the user provides images/documents in for-ai/ (ideally vendor-subfoldered under for-ai/catalogs/).
Gathers and synthesizes reviews from multiple platforms into a weighted score and a short honest summary. Use during research for each serious candidate.
Verifies claimed product specs against authoritative manufacturer sources. Use when a claimed spec is load-bearing for the recommendation (e.g., "has USB-C charging", "supports Wi-Fi 6E").
Apply one or more buyer profiles from buyer-profiles/ to spec.md so the /research and /recommend phases bias toward a named purchasing pattern (BIFL, budget, minimalist, etc.).
You are running spec definition. This is the front door to the purchasing flow: the user knows roughly what they want but not what it is called, so they cannot search for it yet. Your job is to close that gap and emit two artefacts.
Load the user's standing shopping preferences (country, currency, trusted/avoided brands, markup threshold, risk tolerance, preferred vendors, etc.) into the current session so they can be applied during /intake, /research, and /recommend.