Skip to content

rampstackco/claude-skills / skills/product-configurator-design

product-configurator-design

Verified

Designing 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.

references/save-and-share-mechanics.md

View on GitHub
# Save-and-share mechanics

Email-link, account, anonymous, shareable URL, embed.

Configurations users return to or send to others. Multi-decision purchases require deliberation; B2B configurations often need stakeholder review. Save-and-share supports these workflows.

---

## The deliberation-friendly principle

Configurators that serve real decision-making produce configurations users want to save and share.

**The win.** User configures complex purchase. Saves via email-link. Shares with stakeholders. Returns days later. Configuration intact; price unchanged; ready to buy.

**The fail.** User configures; cannot save; loses work between sessions; abandons.

The discipline. Save mechanisms support multi-session and multi-stakeholder workflows.

---

## Pattern A: Email-link save

User enters email; link emailed.

**How it works.**

- "Save and resume later" CTA.
- User enters email.
- Link emailed; user clicks to return.

**Strengths.** No account required; cross-device.

**Weaknesses.** Email deliverability; link expiration.

**When to use.** Default for non-authenticated configurators.

---

## Pattern B: Account-based save

Logged-in users save automatically.

**How it works.**

- User logs in.
- Configurations save to account.
- User returns; finds saved configurations.

**Strengths.** Multi-configuration management.

**Weaknesses.** Account creation friction.

**When to use.** When configurator is part of a logged-in product.

---

## Pattern C: Anonymous-session save

Browser-based persistence.

**How it works.**

- Configuration saved to browser local storage.
- User returns same browser; configuration restored.

**Strengths.** Lowest friction.

**Weaknesses.** Lost on browser change; limited persistence.

**When to use.** As supplement to other patterns.

---

## Pattern D: Shareable URL

Configuration encoded in URL.

**How it works.**

- Configurator encodes the configuration in URL parameters.
- User shares URL; recipient opens; sees same configuration.

**Strengths.** Easy sharing across channels.

**Weaknesses.** URL length; pricing may shift over time.

**When to use.** Shareable configurations; B2B stakeholder review.

---

## Pattern E: Embed code

Configuration embeddable on other sites.

**How it works.**

- Configurator generates embed code.
- User pastes into other sites or proposals.

**Strengths.** Used in B2B proposals.

**Weaknesses.** Cross-site complexity.

**When to use.** B2B sales contexts.

---

## Pattern F: Hybrid

Combining patterns. Common for production configurators.

**Common combination.** Email-link save + shareable URL + anonymous-session backup.

**Strengths.** Multiple paths.

**Weaknesses.** Complexity.

---

## Save trust communication

Users hesitate to save partial sensitive configurations.

**What to communicate.**

- What is saved.
- How long it persists.
- Who can access it.
- How to delete.

The discipline. Trust communication explicit; not buried in privacy policy.

---

## Resume experience

When user returns.

**The principle.** Resume should be uninterrupted.

**The pattern.**

- User clicks recovery link or logs in.
- Lands at the configuration; rest preserved.
- Continues without re-doing.

**Resume failures.**

- Configuration partially preserved; values lost.
- Pricing changed; user surprised.
- Constraint logic shifted; configuration now invalid.

The discipline. Resume preserves; communicate any changes (e.g., "Pricing has updated since you last visited").

---

## Pricing on resume

When prices change between save and resume.

**Honest pattern.** Show the saved configuration with original price; surface "Pricing has changed; updated price is X" with explanation.

**Dishonest pattern.** Silently update price; user does not notice.

The discipline. Honesty about price changes.

---

## Sharing privacy

Shared configurations may include sensitive info.

**Considerations.**

- What is in the URL/embed.
- Who can see it.
- How long links are valid.

The discipline. Sharing respects user privacy; sensitive details may need account-based sharing rather than URL.

---

## Save-and-share analytics

Track usage.

**Metrics.**

- Save rate.
- Resume rate per saved configuration.
- Share rate.
- Configurations completed via save-and-share path.

---

## Common save-and-share failures

**No save mechanism.** Users lose work; abandon.

**Save mechanism brittle.** Links expire; account access broken.

**Resume loses state.** User lands at start; loses work.

**Pricing surprise on resume.** Silent price update.

**Sharing exposes sensitive info.** Embedded URLs share more than intended.

**Save trust missing.** Users do not save because they distrust persistence.

---

## Methodology-level choices that stay in the public skill

The deliberation-friendly principle. Patterns A through F. Save trust communication. Resume experience. Pricing on resume. Sharing privacy. Analytics. Common failures.

## Implementation choices that stay internal

Specific save mechanisms for specific configurators. Specific tooling for URL encoding and embed generation. Privacy review processes. These vary by team.
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: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall