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/constraint-logic-patterns.md
View on GitHub# Constraint logic patterns
Hard, soft, implication, capacity constraints. Communication patterns.
Constraints prevent invalid configurations. Done well, they protect users from errors and surface why; done poorly, they feel arbitrary or fail to prevent invalid configurations.
---
## The protect-and-explain principle
Constraints should prevent invalid configurations and explain why when they engage.
**The win.** User selects Option A. System recognizes A is incompatible with currently-selected Option B. Inline message: "Option A and Option B are incompatible. Choose A or B." User adjusts; understands.
**The fail.** User builds configuration. Submits. Backend rejects. User confused; no path forward.
The discipline. Constraints engage at choice-time; explain why; offer paths.
---
## Pattern A: Hard constraints
Combinations that cannot exist.
**How it works.**
- Two options incompatible; configurator prevents both selected.
- User selects A; B becomes unavailable (greyed; with explanation).
- Or vice versa.
**Strengths.** Prevents invalid configurations.
**Weaknesses.** Can frustrate users who do not understand the constraint.
**When to use.** Genuinely incompatible options.
---
## Pattern B: Soft constraints
Combinations that are unusual but possible.
**How it works.**
- User selects unusual combination.
- System warns: "This combination is unusual. Most teams choose [alternative]."
- User can proceed.
**Strengths.** Respects user agency; provides guidance.
**Weaknesses.** Some users will ignore warning; downstream issues.
**When to use.** Combinations that work but are uncommon.
---
## Pattern C: Implication constraints
When choosing one option requires another.
**How it works.**
- User selects A.
- System auto-selects required B (or surfaces it for selection).
- Explains: "Selecting A requires B because [reason]."
**Strengths.** Prevents missing-dependency errors.
**Weaknesses.** Implication chains can grow complex.
**When to use.** When dependencies are clear and predictable.
---
## Pattern D: Capacity constraints
Configuration exceeds product or fulfillment capacity.
**How it works.**
- User configures heavily; reaches capacity ceiling.
- System caps; explains: "Max [X] supported per configuration."
- Offers contact for custom.
**Strengths.** Prevents impossible configurations.
**Weaknesses.** Can frustrate enterprise audiences; offer contact for custom.
**When to use.** Hard product limits.
---
## Pattern E: Combinatorial constraints
When multiple choices interact in complex ways.
**How it works.**
- Configurator evaluates the full configuration after each change.
- Constraints engage based on combinations, not individual options.
- Surface conflicts as they emerge.
**Strengths.** Handles complex products.
**Weaknesses.** Maintenance complexity.
**When to use.** Products with genuine combinatorial constraints.
---
## Constraint communication
How constraints surface.
**Inline.** Message next to the constrained choice.
**Modal.** Full-screen explanation for major constraints.
**Toast.** Brief notification for minor.
**The discipline.** Match intensity to constraint importance.
---
## Constraint copy
What the message says.
**Strong copy.** "Option A and Option B are incompatible because [specific reason]. Choose A or B."
**Weak copy.** "Invalid configuration."
The discipline. Specific; explanatory; offers paths.
---
## Constraint maintenance
Constraints decay.
**What decays.**
- Constraints from old product variants.
- Constraints inherited from deprecated options.
- New options not yet constrained.
**Maintenance cadence.** Quarterly review with product changes.
---
## Common constraint failures
**Over-constrained.** Too many constraints; user feels boxed in.
**Under-constrained.** User builds invalid configuration; fails downstream.
**Constraint without explanation.** User confused by arbitrary blocking.
**Stale constraints.** Inherited from old product.
**Constraint surface inappropriate.** Modal for minor; toast for major.
**No path offered.** Constraint blocks; user has no alternative.
---
## Methodology-level choices that stay in the public skill
The protect-and-explain principle. Patterns A through E. Constraint communication. Constraint copy. Maintenance. Common failures.
## Implementation choices that stay internal
Specific constraints for specific configurators. Specific copy. Specific tooling. 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 |