rampstackco/claude-skills / skills/product-configurator-design
product-configurator-design
VerifiedDesigning build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics. Honest about infinite-options (decision paralysis), canned-bundles-only (no real customization), and guided-configuration (smart defaults plus meaningful constraints plus escape hatches) patterns. Triggers on configurator design, build-your-own, custom configuration, plan builder, product customizer, configuration tool. Also triggers when users abandon mid-configuration, when configurator conversion is poor, or when a configurator is being scoped for the first time.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 368 B |
| SKILL.md | skill md | 16.3 KB |
| references/common-configurator-failures.md | markdown | 5.0 KB |
| references/configurator-anti-patterns.md | markdown | 4.9 KB |
| references/configurator-decision-criteria.md | markdown | 4.1 KB |
| references/configurator-to-cart-handoff.md | markdown | 4.4 KB |
| references/constraint-logic-patterns.md | markdown | 4.4 KB |
| references/default-configuration-design.md | markdown | 2.9 KB |
| references/real-time-pricing-patterns.md | markdown | 3.9 KB |
| references/save-and-share-mechanics.md | markdown | 5.0 KB |
| references/validation-and-error-patterns.md | markdown | 4.7 KB |
references/common-configurator-failures.md
View on GitHub# Common configurator failures
9+ failure patterns with diagnoses and cures.
---
## "Users abandon halfway through configuration."
**The diagnosis.** Likely infinite-options pattern; too many decisions.
**The cure.** Smart defaults; reduce option count; escape hatches into deeper customization.
---
## "Configurator generates valid-looking configs that fail at fulfillment."
**The diagnosis.** Under-constrained; constraint logic missing.
**The cure.** Add constraint logic. Detail in `references/constraint-logic-patterns.md`.
---
## "Users complain about price surprises at checkout."
**The diagnosis.** Pricing not real-time or hidden until end.
**The cure.** Real-time pricing throughout. Detail in `references/real-time-pricing-patterns.md`.
---
## "Sales says many users contact for help configuring."
**The diagnosis.** Configurator too complex for audience; defaults wrong.
**The cure.** Audit defaults; reduce option exposure; consider canned bundles for simple cases.
---
## "Users save configurations but do not return."
**The diagnosis.** Save mechanism works but follow-up missing.
**The cure.** Reminder email after save; nudge before configuration expires.
---
## "Configurator works on desktop, breaks on mobile."
**The diagnosis.** Mobile UX broken.
**The cure.** Mobile-first design and testing.
---
## "Audience completes but conversion to purchase is low."
**The diagnosis.** Configurator works; commitment friction at handoff.
**The cure.** Audit cart handoff; ensure configuration preserved; reduce checkout friction.
---
## "We added more options; abandonment climbed."
**The diagnosis.** Crossed cognitive-load threshold.
**The cure.** Cut options; surface fewer; defer complexity behind escape hatches.
---
## "Constraint engaged but user did not understand why."
**The diagnosis.** Communication broken.
**The cure.** Constraint copy specific; explains why; offers paths.
---
## "Configurations frequently differ from cart."
**The diagnosis.** Handoff broken.
**The cure.** Test cart handoff. Configuration ID system; single pricing source.
---
## "Sales says enterprise customers want full configurations sales-led."
**The diagnosis.** Enterprise audience wants white-glove; configurator self-serve does not match expectation.
**The cure.** Enterprise path: configurator surfaces "Talk to sales for custom" for above-threshold configurations.
---
## "We A/B tested adding more options; conversion went down."
**The diagnosis.** Crossed the threshold.
**The cure.** More is not always better. Maintain option discipline.
---
## "Returning users see different prices than they saved."
**The diagnosis.** Pricing shifted; configurator silently updated.
**The cure.** Honest about price changes on resume.
---
## "Mobile configuration completion is half of desktop."
**The diagnosis.** Mobile UX significantly worse.
**The cure.** Mobile-first redesign; reduce option exposure on mobile.
---
## "Validation rejects valid international inputs."
**The diagnosis.** Validation too strict.
**The cure.** Audit validation rules; allow international formats.
---
## "Some configurations work; others fail post-checkout."
**The diagnosis.** Constraint logic incomplete; some invalid combinations slip through.
**The cure.** Audit constraints. Add missing rules.
---
## "Configurator's average configuration is more expensive than baseline."
**The diagnosis.** May not be a problem (real customization adds cost) or may be (default biased toward expensive).
**The cure.** Audit defaults. Defaults should reflect typical use, not flatter revenue.
---
## "Sales pipeline shrunk after configurator launch; people self-serve."
**The diagnosis.** Configurator absorbed the audience that would have called.
**The cure.** This may be intentional (cost reduction) or unintentional (loss of complex deals). Decide if the shift is desired.
---
## "Configurator launched; analytics broke."
**The diagnosis.** Instrumentation missed.
**The cure.** Verify analytics post-launch. Per-step instrumentation for diagnostic.
---
## The pattern across failures
Most configurator failures fall into one of three patterns.
**Pattern 1: Cognitive overload.** Infinite-options, too many decisions, no defaults. The fix is guided-configuration.
**Pattern 2: Trust damage.** Hidden pricing, price drift, unclear constraints, lost state. The fix is transparency.
**Pattern 3: Handoff failures.** Cart loses configuration; checkout disappears it. The fix is loop closure.
The metric pattern: configurator failures often look fine on engagement. Signal is in completion rate, conversion to purchase, downstream order accuracy.
---
## Methodology-level choices that stay in the public skill
The catalog of failure patterns with diagnoses and cures. The pattern across failures (cognitive overload, trust damage, handoff). The principle that engagement alone is insufficient.
## Implementation choices that stay internal
Specific failure cases the team has encountered. Specific dashboards. Specific cures. The team's audit and retirement processes. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |