marketplace-personalisation
Use this skill whenever designing, building, debugging, reviewing, or improving a personalisation or recommendation system for a two-sided trust marketplace built on AWS Personalize — covers event tracking, dataset and schema design, two-sided matching, cold start, feedback loops, bias control, recipe selection, serving-time re-ranking, observability, and a diagnostic playbook for existing systems. Trigger even when the user does not explicitly mention "AWS Personalize" but is working on recommendations, ranking, search, homepage personalisation, or anything that matches seekers and providers across a trust-based catalog.
What this skill does
# Marketplace Engineering Two-Sided Personalisation Best Practices Comprehensive guide for designing, building and improving personalisation and recommendation systems in two-sided trust marketplaces on AWS Personalize. Contains 49 rules across 9 categories, ordered by cascade impact on the personalisation lifecycle, plus two playbooks for planning a new system from scratch and diagnosing an existing one. ## When to Apply Reference this skill when: - Designing the event schema and tracking for a new recommender system - Choosing an AWS Personalize recipe (USER_PERSONALIZATION_v2, SIMS, PERSONALIZED_RANKING_v2) - Writing or reviewing candidate-generation and re-ranking code for marketplace search or homefeed - Handling cold start for new providers, new seekers, or new catalog regions - Diagnosing a live system that "mostly works but feels stale, unfair, or unpersonalised" - Planning the next experiment, baseline comparison, or A/B test for the recommender - Investigating concentration, coverage collapse, death spirals, or training-serving skew - Adding observability dashboards, drift detection, or online metric slicing ## Setup This skill has no user-specific configuration — it is self-contained. References are live URLs to official AWS Personalize documentation, academic papers on bias and exposure, and engineering blogs from Airbnb and DoorDash. ## Rule Categories Categories are ordered by cascade impact: earlier stages poison everything downstream. | # | Category | Prefix | Impact | |---|----------|--------|--------| | 1 | Event Tracking and Capture | `track-` | CRITICAL | | 2 | Dataset and Schema Design | `schema-` | CRITICAL | | 3 | Two-Sided Matching Patterns | `match-` | CRITICAL | | 4 | Simple Baselines and Theory of Constraints | `simple-` | HIGH | | 5 | Feedback Loops and Bias Control | `loop-` | HIGH | | 6 | Cold Start and Coverage | `cold-` | HIGH | | 7 | Recipe and Pipeline Selection | `recipe-` | MEDIUM-HIGH | | 8 | Inference, Filters and Re-ranking | `infer-` | MEDIUM-HIGH | | 9 | Observability and Online Metrics | `obs-` | MEDIUM-HIGH | ## Quick Reference ### 1. Event Tracking and Capture (CRITICAL) - [`track-log-impressions-alongside-clicks`](references/track-log-impressions-alongside-clicks.md) — the denominator that turns clicks into a rate and unlocks unbiased training - [`track-use-stable-opaque-item-ids`](references/track-use-stable-opaque-item-ids.md) — prevents history loss when listings rename or move - [`track-stamp-events-with-request-id`](references/track-stamp-events-with-request-id.md) — the join key that enables impression-to-outcome attribution - [`track-stream-events-via-putevents`](references/track-stream-events-via-putevents.md) — real-time adaptation versus end-of-day bulk import - [`track-capture-negative-signals`](references/track-capture-negative-signals.md) — dismissal is information, silence is not - [`track-measure-outcomes-not-clicks`](references/track-measure-outcomes-not-clicks.md) — reward the completed booking, not the clickbait ### 2. Dataset and Schema Design (CRITICAL) - [`schema-design-conservatively`](references/schema-design-conservatively.md) — Interactions schemas are immutable, Users/Items are painful to change - [`schema-keep-user-item-thin`](references/schema-keep-user-item-thin.md) — volatile fields belong in events - [`schema-enforce-metadata-freshness`](references/schema-enforce-metadata-freshness.md) — PutItems on every metadata change - [`schema-prefer-categorical-fields`](references/schema-prefer-categorical-fields.md) — unlock per-value features - [`schema-weight-event-value`](references/schema-weight-event-value.md) — align the model with the business outcome - [`schema-include-context-everywhere`](references/schema-include-context-everywhere.md) — train-serve feature parity - [`schema-meet-minimum-dataset-sizes`](references/schema-meet-minimum-dataset-sizes.md) — 50 users / 50 items / 1000 interactions before training ### 3. Two-Sided Matching Patterns (CRITICAL) - [`match-rank-mutual-fit`](references/match-rank-mutual-fit.md) — rank by mutual accept probability - [`match-hard-filter-before-ranking`](references/match-hard-filter-before-ranking.md) — retrieval enforces feasibility - [`match-cap-provider-exposure`](references/match-cap-provider-exposure.md) — diversity as a fairness constraint - [`match-model-capacity-constraints`](references/match-model-capacity-constraints.md) — capacity-discounted scoring - [`match-balance-supply-demand`](references/match-balance-supply-demand.md) — per-segment strategy routing ### 4. Simple Baselines and Theory of Constraints (HIGH) - [`simple-ship-popularity-baseline`](references/simple-ship-popularity-baseline.md) — a reference point that every ML model must beat - [`simple-find-bottleneck-first`](references/simple-find-bottleneck-first.md) — diagnostic before optimisation - [`simple-heuristic-rerank-cold-cohorts`](references/simple-heuristic-rerank-cold-cohorts.md) — trust × recency × proximity - [`simple-budget-complexity`](references/simple-budget-complexity.md) — ship or kill criterion before running - [`simple-audit-before-build`](references/simple-audit-before-build.md) — telemetry audit gates model work - [`simple-measure-gap-to-baseline`](references/simple-measure-gap-to-baseline.md) — baseline retained as permanent minority bucket ### 5. Feedback Loops and Bias Control (HIGH) - [`loop-log-ranking-slot`](references/loop-log-ranking-slot.md) — slot data for position-bias correction - [`loop-reserve-random-exploration`](references/loop-reserve-random-exploration.md) — unbiased training data - [`loop-optimize-completed-outcome`](references/loop-optimize-completed-outcome.md) — reward the goal, not the proxy - [`loop-decay-event-weights`](references/loop-decay-event-weights.md) — old preferences fade - [`loop-detect-death-spirals`](references/loop-detect-death-spirals.md) — exposure Gini as a leading indicator ### 6. Cold Start and Coverage (HIGH) - [`cold-use-v2-recipe-with-metadata`](references/cold-use-v2-recipe-with-metadata.md) — metadata extrapolates to new listings - [`cold-best-of-segment-popularity`](references/cold-best-of-segment-popularity.md) — segmentation beats global top-N - [`cold-capture-onboarding-intent`](references/cold-capture-onboarding-intent.md) — ask instead of guessing - [`cold-reserve-exploration-slots`](references/cold-reserve-exploration-slots.md) — promotions filter for fresh inventory - [`cold-tag-cold-start-recs`](references/cold-tag-cold-start-recs.md) — warm-versus-cold metric slicing ### 7. Recipe and Pipeline Selection (MEDIUM-HIGH) - [`recipe-default-to-user-personalization-v2`](references/recipe-default-to-user-personalization-v2.md) — discovery default - [`recipe-sims-for-item-page-only`](references/recipe-sims-for-item-page-only.md) — similar-items is not a homepage recipe - [`recipe-personalized-ranking-as-reranker`](references/recipe-personalized-ranking-as-reranker.md) — not a candidate generator - [`recipe-build-candidate-rerank-pipeline`](references/recipe-build-candidate-rerank-pipeline.md) — two layers, two concerns - [`recipe-defer-hpo-until-baseline-measured`](references/recipe-defer-hpo-until-baseline-measured.md) — prove the model before tuning ### 8. Inference, Filters and Re-ranking (MEDIUM-HIGH) - [`infer-use-filters-api`](references/infer-use-filters-api.md) — Personalize backfills to numResults - [`infer-rerank-rules-after-model`](references/infer-rerank-rules-after-model.md) — preserve the model distribution - [`infer-deduplicate-canonical-entity`](references/infer-deduplicate-canonical-entity.md) — provider-level dedup, not listing-level - [`infer-enforce-exposure-caps`](references/infer-enforce-exposure-caps.md) — rolling fairness constraints - [`infer-cache-responses-short-ttl`](references/infer-cache-responses-short-ttl.md) — session continuity and cost control ### 9. Observability and Online Metrics (MEDIUM-HIGH) - [`obs-always-ab-test`](references/obs
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.