product-configurator-design
The product-configurator-design skill provides guidance for building customizable product interfaces like Tesla vehicle configurators or pricing plan builders, emphasizing constraint logic, real-time pricing, and smart defaults to guide users through configuration without overwhelming them. Use this skill when designing a configurator for the first time, addressing high abandonment rates, defining which product parameters deserve customization exposure versus sensible defaults, or validating whether your product needs true customization versus simplified bundled options.
git clone --depth 1 https://github.com/rampstackco/claude-skills /tmp/product-configurator-design && cp -r /tmp/product-configurator-design/dist/pi/.agents/skills/product-configurator-design ~/.claude/skills/product-configurator-designSKILL.md
# Product Configurator Design A senior product marketing director's playbook for designing build-your-own product configurators. Tesla-style vehicle configurators, custom-pricing builders, plan-builders, product customizers. Constraint logic, real-time pricing, validation, save-and-share mechanics. The discipline of building a configurator that produces configurations users actually commit to. Most configurators fail in one of two ways. They expose every parameter at full granularity (47 toggles, 12 sliders) and produce decision paralysis; users abandon halfway through. Or they pretend to be configurators but are actually three pre-built bundles labeled "Custom"; the configurator framing was marketing while the product is bundles. The configurators that work do something different. Smart defaults that produce a sensible starting configuration; meaningful constraints that prevent invalid combinations and surface why; escape hatches into deeper customization for users who want it; real-time pricing that responds to choices. Users feel guided rather than overwhelmed. The voice is the senior product marketing director who has watched configurators double conversion when redesigned with smart defaults and watched them collapse when "more options" were added without constraint logic. Practical, opinionated about the constraints that protect users from themselves, willing to call out when canned bundles are the right answer. When to use this skill: scoping a build-your-own configurator for the first time, auditing a configurator with high abandonment, designing the constraint logic that prevents invalid combinations, or deciding which parameters earn exposure vs which should default. --- ## What this skill covers This skill spans build-your-own product configurators. The growth-tooling distinctions: - `calculator-design` is calculators that give a number from inputs. This skill builds a product configuration with multiple decisions. - `comparison-tool-design` is comparing known options. This skill builds a custom option. - `multi-step-form-design` is data capture. This skill is configuration design. - **`product-configurator-design` (this skill)** is constraint logic, real-time pricing, validation, save-and-share, and configurator-to-cart handoff. - `pm-spec-writing` is the spec for engineers building the configurator. The audience: product marketers, growth marketers, ecommerce teams, B2B teams shipping configurable products, agencies running configurator work for clients. Out of scope: calculator design (covered by `calculator-design`); comparison tools (covered by `comparison-tool-design`); the engineering implementation; specific configurator-platform configurations (those stay implementation-side). --- ## The configurator decision: when configurators earn investment vs when bundles suffice Before designing the configurator, decide whether a configurator is the right answer. **Configurators earn investment when:** - The product has genuinely customizable parameters that affect outcome and cost. - The audience values customization beyond what bundles offer. - The team can support the configuration logic (validation, pricing, fulfillment). - The combinatorial space is meaningful but constrained (not literally infinite). **Configurators do NOT earn investment when:** - The product is essentially bundles. Calling them "configurations" is marketing, not product. - The audience does not value customization. Some audiences want to choose from curated options, not build. - The combinatorial space is so large that no audience can navigate it. - Customization produces invalid combinations the team cannot prevent. - A simpler comparison or selection tool would serve. The decision is not "should we have a configurator"; it is "is the configurator the right tool for this product and audience." Detail in [`references/configurator-decision-criteria.md`](references/configurator-decision-criteria.md). --- ## Infinite-options vs canned-bundles-only vs guided-configuration The keystone framing. **Infinite-options.** Every parameter exposed at full granularity. 47 toggle switches and 12 sliders. Decision paralysis. Users abandon halfway through; few complete a configuration. Cost: design effort produces a configurator nobody completes; conversion suffers. **Canned-bundles-only.** "Configurator" that is actually three pre-built bundles labeled Basic/Pro/Enterprise. No real customization. The configurator framing was marketing; the product is bundles. Cost: audience that came expecting customization feels deceived; conversion suffers because expectations did not match reality. **Guided-configuration.** Smart defaults that produce a sensible starting configuration; meaningful constraints that prevent invalid combinations; escape hatches into deeper customization for users who want it; real-time pricing that responds to choices. Cost: design effort upfront is significant; conversion typically improves meaningfully because users complete configurations they commit to. The litmus test. Hand the configurator to a stranger in the target audience. Do they reach a configuration they would actually buy in under 5 minutes without expert help? If yes, guided-configuration. If they paralyze at the options, infinite-options. If they only see bundles, canned-bundles-only. --- ## Default-configuration design The starting point. **The principle.** The configurator opens with a sensible default configuration. The user adjusts from there. **Default selection.** - The configuration most audiences would choose. - Reflects audience research (sales-call mining, prior configurations). - Inferable from referrer, query, or stated preference. **Default presentation.** - Default visible immediately; user sees a complete configuration with price. - Adjust controls obvious; user knows what is changeable. - Reset-to-default available; users who experiment can return. **The blank-canvas trap.** Configurato
Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.
How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.
Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, write a creative direction document, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables.
Plan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.