Claude Code plugin: purchasing workflow — intake, research, compare, evaluate, recommend, market-check, preference memory, and hardware-rig profiling primitives, with general/tech-procurement/recommendations variants.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin purchasingApply 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.).
Generate a focused comparison of 2–4 specific products without going through the full research/recommend flow. Useful when the user has narrowed down candidates and wants to scan them side by side.
Quick one-off evaluation of a single product against the current spec
Extract product information from screenshots, PDFs, and catalog images in `for-ai/` into a structured CSV at `data/extracted/products.csv`.
You are running the intake for this purchase. The goal is to populate `spec.md` at the repo root with the per-purchase brief.
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`.
Compare local market prices against international RRP with import-cost realism
List recent recommendations from the recommendations/ folder with their feedback status (liked, disliked, no-response, queued).
Record like/dislike/nuanced feedback against a past recommendation and update the preference profile so future suggestions improve.
User provides something they enjoyed (a film, book, podcast, video, course, etc.); the recommender suggests similar items they might also enjoy, grounded in the preference profile.
First-run setup for the recommendation workspace — picks format, captures initial preferences, builds the folder structure, and suggests MCPs.
Parse an OPML file (typically a podcast subscription export) from ingest/opml/ and use it to seed/update the preference profile.
Parse a reading list export (Goodreads, StoryGraph, Pocket, Instapaper, Readwise, etc.) from ingest/reading-list/ and use it to seed/update the preference profile.
Parse a watch history export (Netflix, Trakt, Letterboxd, JustWatch, etc.) from ingest/watch-history/ and use it to seed/update the preference profile.
Produce the final recommendation as a Typst-compiled PDF at `from-ai/report.pdf`.
Re-run the shortlist against the current spec and write a new dated recommendations file
Evaluate all candidate products against the spec and produce `from-ai/research.md`.
You are analyzing the user's hardware configuration to identify bottlenecks, compatibility issues, and upgrade opportunities.
You are helping the user compare specific components to make an informed purchasing decision.
You are creating a formal cost estimate document that can be used for internal approval, accountant review, or VAT deduction purposes.
You are documenting the hardware specifications for a machine. This profile will be used for compatibility analysis and upgrade recommendations.
You are generating specific component recommendations based on the user's hardware analysis, preferences, and budget.
You are conducting the initial user interview to set up this hardware planning workspace. This is a structured interview process to gather all context needed for effective hardware upgrade planning.
Run a one-time setup (or update) for the user's standing shopping preferences, and save them to memory (Mem0 MCP) so every future purchase workspace can `/load-preferences` them.
Update spec.md with an addition, edit, or removal — diff-only response
Researches manufacturer reputation, history, support quality, and regional presence. Use before recommending any product from an unfamiliar brand.
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/).
Generates targeted content recommendations grounded in the user's preference profile and feedback history. Writes one markdown file per recommendation under recommendations/ with reasoning and metadata.
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").
Claude Code plugin for running purchasing decisions end-to-end — from intake and spec, through research and comparison, to a recommendation and (optionally) a PDF report. Covers three purchasing surfaces: general consumer/business purchasing, technical rig procurement, and vendor/content recommendations.
Part of the danielrosehill Claude Code marketplace.
General-purchasing commands (/purchasing:*):
intake — build the per-purchase spec (spec.md)research — evaluate candidates against the speccompare — side-by-side comparison of 2–4 shortlisted productsevaluate — quick one-off evaluation of a single productrecommend — generate the final PDF recommendation reportrecompare — re-run the shortlist against the current specextract — pull product data from screenshots, PDFs, and catalogsmarket-check — local vs international price realism with import costsload-preferences / save-preferences — standing preferences to/from Mem0apply-profile — bias this purchase toward a named buyer archetype (BIFL, budget, minimalist, etc.)update-spec — targeted edit to spec.mdTech-procurement commands (/purchasing:rig-*):
rig-setup — initial hardware-planning interviewrig-profile — document a specific machine's hardwarerig-analyze — identify bottlenecks and upgrade opportunitiesrig-compare — compare specific componentsrig-recommend — generate upgrade recommendationsrig-estimate — produce a formal cost estimate documentVendor-recommendations commands (/purchasing:rec-*):
rec-onboard — first-run preference capture (format + availability)rec-more-like-this — similar-item recommendations from a seedrec-log-feedback — record like / dislike on past recommendations and update the profilerec-list — surface recommendation history and feedback statusrec-opml-ingest / rec-reading-list-ingest / rec-watch-history-ingest — bulk-seed preferences from exportsAgents:
manufacturer-research, price-comparison, product-extraction, review-aggregation, spec-verification — research sub-agents for the general-purchasing flowpreference-curator, recommender — recommendation-profile and suggestion sub-agents/purchasing:new-workspace <name> [--variant=general-purchasing|tech-procurement|vendor-recommendations] [--local-only] [--private]Scaffolds a new workspace from one of three templates, personalises CLAUDE.md from ~/.claude/CLAUDE.md, and (by default) creates a public GitHub repo for it.
Primitives live in the plugin → globally available from any cwd.
Workspace scaffolds are provisioned as data → no .claude/ tree inside provisioned workspaces.
Plugin updates never touch your workspace data.
See PLAN.md in Claude-Workspace-Reshaping-190426 for the full pattern spec this plugin follows.
general-purchasing (default) — one-purchase-per-repo workflow with spec, buyer profiles, research, and PDF report.tech-procurement — hardware rig planning: profile existing machines, analyse bottlenecks, recommend components, produce a formal cost estimate.vendor-recommendations — ongoing content/vendor recommendation workspace: learns preferences over time, generates similar-item suggestions, tracks feedback.Via the danielrosehill marketplace:
/plugin marketplace add danielrosehill/Claude-Code-Plugins
/plugin install purchasing
MIT.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive PR review agents specializing in comments, tests, error handling, type design, code quality, and code simplification
Meta-prompting and spec-driven development system for Claude Code. Productivity framework for structured AI-assisted development.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim