New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Product Configurator Design

by rampstackco in rampstackco/claude-skills

Designing build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics.

MITAuto-check passedBackend & APIs

Install Product Configurator Design

skills CLI
$ npx skills add rampstackco/claude-skills --skill product-configurator-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rampstackco/claude-skills product-configurator-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rampstackco/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-configurator-design .claude/skills/product-configurator-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-configurator-design
GitHub stars
941
Token cost
~4.2k tokens
SKILL.md length
1,787 words
Files
11 (incl. references)
Skills in repo
103
Repo updated
First seen
Licence
MIT

At a glance

Designing build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics.

  • Works in 12 steps: The configurator decision. Is… → Guided-configuration, not… → Default configuration sensible. User… → …
  • Configurator design
  • SKILL.md covers What this skill covers, The configurator decision:…, Infinite-options vs… and Default-configuration design, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Configurator Design is an agent skill from rampstackco/claude-skills. 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…

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `references/common-configurator-failures.md` and `references/configurator-anti-patterns.md`).

It sits in Backend & APIs, covering Payments and billing. The repository describes itself as: Stack-agnostic Claude Skills covering the full website lifecycle: brand, design, content, SEO, dev, ops, growth, and research. Build, ship, audit, optimize. The licence is MIT.

When your agent uses it

  • Configurator design
  • Custom configuration
  • Product customizer
  • Configuration tool

Example prompts

  • “/product-configurator-design”

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

  1. The configurator decision. Is configurator the right tool, or do bundles serve?
  2. Guided-configuration, not infinite-options or canned-bundles-only. Smart defaults plus meaningful constraints plus escape hatches.
  3. Default configuration sensible. User adjusts from default; does not build from zero.
  4. Constraint logic prevents invalid combinations. Hard, soft, implication, capacity constraints.
  5. Constraint communication clear. Why constraint engaged; what user can do.
  6. Real-time pricing visible. Price updates with choices; breakdown available.
  7. Validation helpful. Inline; specific; offers paths.
  8. Save-and-share works. Multi-session; shareable; B2B-friendly.
  9. Configurator-to-cart handoff preserves state. Cart shows configuration.
  10. Mobile parity. Configurator works on the devices the audience uses.
  11. Conversion as success metric. Not just completion rate; downstream purchase.
  12. Maintenance discipline. Configurations updated as product changes; quarterly audit.

What it can do on your machine

Read from SKILL.md and the folder at commit 482c9bf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Configurator Design loads about 4.2k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 169 tokens; SKILL.md has 1,787 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~169
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rampstackco/claude-skills at commit 482c9bf, republished under its MIT licence (© rampstackco). 1,787 words, ~4,186 tokens.

Download SKILL.mdSave it as .claude/skills/product-configurator-design/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
product-configurator-design
description
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.
category
growth-tooling
catalog_summary
Designing interactive product configurators. Distinguishes infinite-options (decision paralysis from too many options) from canned-bundles-only (no real…
display_order
12

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.

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. Configurator opens empty; user must build from scratch. Decision paralysis at the start.

The cure. Default-heavy. The user adjusts; never builds from zero.

Detail in references/default-configuration-design.md.

Constraint logic

Preventing invalid combinations; surfacing why.

The principle. The configurator should not let users build invalid configurations (combinations that cannot ship, cannot be priced, or do not work together). When constraints engage, the configurator surfaces why.

Constraint patterns.

  • Hard constraints. "Option A and Option B are incompatible." Configurator prevents the combination; explains why.
  • Soft constraints. "Combining Option A with Option C is unusual but possible." Configurator allows; warns.
  • Implication constraints. "Selecting Option A requires Option D." Configurator auto-includes D; explains.
  • Capacity constraints. "This configuration exceeds shipping capacity." Configurator caps; explains.

Constraint communication.

  • Why this constraint engaged.
  • What user can do (different option, contact for custom).
  • No friction-only blocking; always offer a path.

The over-constrained trap. Too many constraints; user feels boxed in.

The under-constrained trap. User builds configuration that fails at checkout or fulfillment.

Detail in references/constraint-logic-patterns.md.

Real-time pricing and impact display

Pricing that responds to choices.

The principle. Price updates as the user adjusts. The user sees the cost impact of each choice immediately.

Strong pricing display.

  • Total price prominent and updated in real time.
  • Per-choice impact visible ("Adds $X" or "Saves $X").
  • Breakdown available ("How is this priced").
  • Currency and locale appropriate.

Weak pricing display.

  • Price hidden until the end.
  • Per-choice impact invisible; user does not know what each option costs.
  • Breakdown not available; total is opaque.

The price-shock trap. User configures heavily; reaches checkout; sees a price they did not expect; abandons.

The cure. Price visible throughout. No surprises at checkout.

Detail in references/real-time-pricing-patterns.md.

Validation and error patterns

When the configurator catches invalid input.

The principle. Validation should be helpful, not punitive.

Validation patterns.

  • Inline validation. Error appears next to the invalid choice.
  • Pre-emptive validation. Constraint logic prevents the error from being possible.
  • Final validation. Pre-checkout review surfaces any remaining issues.

Error communication.

  • Specific to the issue.
  • Explains why.
  • Offers a path (alternative option, contact for custom).

The validation-strict trap. Validation rejects valid edge-case inputs.

The validation-loose trap. Configurator accepts inputs that fail downstream.

Detail in references/validation-and-error-patterns.md.

Show full SKILL.md (691 more words)Show less

Save-and-share mechanics

Configurations users return to or send to others.

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

Save patterns.

  • Email-link save. User enters email; configuration link emailed.
  • Account-based save. Logged-in users save automatically.
  • Anonymous-session save. Browser-based persistence.

Share patterns.

  • Shareable URL. Configuration encoded in URL; share via any channel.
  • Embed code. Configuration embeddable on other sites or in proposals.
  • Email share. Direct email-to-recipient with configuration.

Why save-and-share matters.

  • Multi-decision purchases require deliberation.
  • B2B configurations often need stakeholder review.
  • Returning users continue rather than restart.

Detail in references/save-and-share-mechanics.md.

Configurator-to-cart handoff

When the user commits.

The principle. Handoff from configurator to cart should preserve the configuration entirely.

Handoff patterns.

  • Configuration becomes the cart item.
  • Cart shows the configuration summary.
  • Edit-from-cart returns to configurator with state preserved.

The handoff failure. Configuration partially preserved; cart shows a generic SKU; user cannot tell if their custom build is reflected.

The cure. Handoff loop closed. Configuration visible in cart; price matches; edits possible.

Detail in references/configurator-to-cart-handoff.md.

Common failure modes

Rapid-fire. Diagnoses in references/common-configurator-failures.md.

  • "Users abandon halfway through configuration." Likely infinite-options pattern; too many decisions.
  • "Configurator generates valid-looking configs that fail at fulfillment." Under-constrained; constraint logic missing.
  • "Users complain about price surprises at checkout." Pricing not real-time or hidden until end.
  • "Sales says many users contact for help configuring." Configurator too complex for audience; defaults wrong.
  • "Users save configurations but do not return." Save mechanism works but follow-up missing.
  • "Configurator works on desktop, breaks on mobile." Mobile UX broken.
  • "Audience completes but conversion to purchase is low." Configurator works; commitment friction at handoff.
  • "We added more options; abandonment climbed." Crossed the cognitive-load threshold.
  • "Constraint engaged but user did not understand why." Communication broken; users feel arbitrarily blocked.

The framework: 12 considerations for configurator design

When designing or auditing a configurator, walk these 12 considerations.

  1. The configurator decision. Is configurator the right tool, or do bundles serve?
  2. Guided-configuration, not infinite-options or canned-bundles-only. Smart defaults plus meaningful constraints plus escape hatches.
  3. Default configuration sensible. User adjusts from default; does not build from zero.
  4. Constraint logic prevents invalid combinations. Hard, soft, implication, capacity constraints.
  5. Constraint communication clear. Why constraint engaged; what user can do.
  6. Real-time pricing visible. Price updates with choices; breakdown available.
  7. Validation helpful. Inline; specific; offers paths.
  8. Save-and-share works. Multi-session; shareable; B2B-friendly.
  9. Configurator-to-cart handoff preserves state. Cart shows configuration.
  10. Mobile parity. Configurator works on the devices the audience uses.
  11. Conversion as success metric. Not just completion rate; downstream purchase.
  12. Maintenance discipline. Configurations updated as product changes; quarterly audit.

The output of the framework is a configurator that earns the configuration that ships, with constraint logic, pricing, and handoff working together to produce commitments users keep.

Reference files

Closing: configurators earn investment when they earn the configuration that ships

The configurators that work as compounding assets are the ones that produce configurations users commit to. Not 50-cell decision matrices. Not bundles dressed as configurators. Configurations the user built, priced, validated, saved, and bought.

That is the bar. Below the bar are infinite-options (decision paralysis; users abandon) and canned-bundles-only (configurator framing without real customization; users feel deceived). Above the bar are guided-configuration tools where smart defaults, meaningful constraints, real-time pricing, validation, and save-and-share work together to produce commitments.

The discipline is in the design choices. The decision to build a configurator at all. The default configuration that opens the experience. The constraint logic that protects users from invalid combinations. The pricing that updates with choices. The validation that helps without punishing. The save-and-share that supports multi-decision purchases. The cart handoff that preserves the configuration. The maintenance that keeps the configurator in sync with the product it represents.

© rampstackco, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/product-configurator-design of rampstackco/claude-skills.

  • SKILL.md
  • README.md
  • references/common-configurator-failures.md
  • references/configurator-anti-patterns.md
  • references/configurator-decision-criteria.md
  • references/configurator-to-cart-handoff.md
  • references/constraint-logic-patterns.md
  • references/default-configuration-design.md
  • references/real-time-pricing-patterns.md
  • references/save-and-share-mechanics.md
  • references/validation-and-error-patterns.md

Open the folder on GitHubat commit 482c9bf

Compare with similar skills

Product Configurator Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Configurator Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Configurator Design this skillrampstackco/claude-skills941—~4.2kAutomated safety check: PassMIT
Billing Automationwshobson/agents40k13 repos~473Automated safety check: PassMIT
Stripe Best Practicesfossasia/eventyay1.7k1 repos~1.7kAutomated safety check: PassApache-2.0
Pinme Uniwebpayglitternetwork/pinme3.7k—~7.3kAutomated safety check: PassMIT
PayRam Payment AnalyticsPayRam/payram-mcp158—~4.1kAutomated safety check: PassNone
Test Convt Serveropencoredev/convt258—~1.6kAutomated safety check: PassAGPL-3.0

Similar skills

  • Billing Automation

    wshobson/agents

    Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.

    40k GitHub starsUsed in 13 repos~473 tokens
    Backend & APIsAuto-check passed

  • Stripe Best Practices

    fossasia/eventyay

    Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…

    1.7k GitHub starsUsed in 1 repo~1.7k tokens
    Backend & APIsAuto-check passed

  • Pinme Uniwebpay

    glitternetwork/pinme

    A skill your agent uses when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout…

    3.7k GitHub stars~7.3k tokensUpdated 27 days ago
    Backend & APIsAuto-check passed

  • PayRam Payment Analytics

    PayRam/payram-mcp

    Queries a PayRam server's dashboard data through its REST APIs with a Bearer token: payment search, daily volume, unswept balances, sweep history and on-ramp metrics.

    158 GitHub stars~4.1k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Test Convt Server

    opencoredev/convt

    Run and verify the convt jobs API, Postgres queue, object storage, sandbox worker and metering locally.

    258 GitHub stars~1.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • AWS Marketplace Metering

    aws/agent-toolkit-for-aws

    Official

    Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…

    2.8k GitHub stars~18k tokensUpdated today
    Backend & APIsAuto-check passed

More from rampstackco/claude-skills

All 103 skills in this repo

  • After Action Report

    rampstackco/claude-skills

    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.

    941 GitHub stars~2.5k tokensUpdated 2 days ago
    Auto-check passed

  • Analytics Strategy

    rampstackco/claude-skills

    Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy.

    941 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Brand Style Guide

    rampstackco/claude-skills

    Build or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts.

    941 GitHub stars~2.1k tokensUpdated 2 days ago
    Auto-check passed

  • Brand Voice

    rampstackco/claude-skills

    Develop or document a complete brand voice and tone system covering voice attributes, tone shifts by context, vocabulary preferences, grammar rules, and copy examples.

    941 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

  • Content And Copy

    rampstackco/claude-skills

    Write or edit website copy, blog content, and editorial pieces with attention to voice, structure, and goal.

    941 GitHub stars~2.1k tokensUpdated 2 days ago
    Auto-check passed

  • Content Strategy

    rampstackco/claude-skills

    Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning.

    941 GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Product Configurator Design

What does Product Configurator Design do?

Designing build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics. Product Configurator Design is an agent skill from rampstackco/claude-skills. Designing build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics.

When should I use Product Configurator Design?

Product Configurator Design fits situations like: configurator design; custom configuration; product customizer; configuration tool.

How do I install Product Configurator Design in Claude Code?

Run `npx skills add rampstackco/claude-skills --skill product-configurator-design -a claude-code`. Or copy the skill folder (skills/product-configurator-design in rampstackco/claude-skills) into .claude/skills/product-configurator-design in your project. Claude Code loads it when a task matches its description.

How do I install Product Configurator Design in Codex?

Run `npx skills add rampstackco/claude-skills --skill product-configurator-design -a codex`. Or copy the skill folder (skills/product-configurator-design in rampstackco/claude-skills) into .agents/skills/product-configurator-design in your project. Codex loads it when a task matches its description.

Can I use Product Configurator Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rampstackco/claude-skills --skill product-configurator-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-configurator-design, .gemini/skills/product-configurator-design, .github/skills/product-configurator-design and .opencode/skills/product-configurator-design in your project.

What does Product Configurator Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Configurator Design is instructions for the agent only.

Does Product Configurator Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Configurator Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Configurator Design use?

Product Configurator Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Configurator Design use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Product Configurator Design?

Skills that share tags, products or a category with Product Configurator Design: Billing Automation (wshobson/agents, 40k stars), Stripe Best Practices (fossasia/eventyay, 1.7k stars), Pinme Uniwebpay (glitternetwork/pinme, 3.7k stars) and PayRam Payment Analytics (PayRam/payram-mcp, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Configurator Design?

rampstackco (a GitHub organization) maintains it in rampstackco/claude-skills, which has 941 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 7, 2026.

Source: rampstackco/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.