card-variant-registry

List merch-card variants with field schemas, CSS classes, and slot mappings.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/adobecom/mas-claude-config --skill card-variant-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: card-variant-registry
Source: https://github.com/adobecom/mas-claude-config/tree/main/config/skills/card-variant-registry
Command: npx skills add https://github.com/adobecom/mas-claude-config --skill card-variant-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive reference for all merch-card variants, their field schemas, CSS classes, and slot mappings, simplifying the process of adding new variants, debugging rendering issues, and understanding variant differences.

Core Features & Use Cases

  • Variant Registry: Access detailed information on all available merch-card variants.
  • Schema and Class Information: Understand the field schemas and CSS classes for each variant.
  • Slot Mapping: Identify how slots map to editor fields for precise control.
  • Use Case: When you need to add a new variant, debug rendering issues, or compare variant schemas.

Quick Start

Use the card-variant-registry skill to list all card variants.

Frequently Asked Questions about card-variant-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage merch-card variants and their CSS classes?

You can manage merch-card variants by accessing a comprehensive registry that provides detailed field schemas, CSS classes, and slot mappings for each available card configuration. This simplifies variant management and debugging.

How do I map slots to editor fields for web-component merch-cards?

Slot mapping for merch-cards identifies how slots map to editor fields for precise control over web-component rendering. The registry provides detailed field schemas and configurations to ensure accurate slot assignments.

Why does my merch-card rendering issue happen and how can I debug it?

Debugging merch-card rendering issues requires understanding the variant's specific field schemas, CSS classes, and slot mappings. The registry assists by providing a detailed reference to compare variant configurations and identify discrepancies.

Do I need to know web-component architecture to use the card variant registry?

Yes, using the card variant registry requires knowledge of web-component architecture and CSS styling. This prerequisite knowledge is necessary to understand field schemas, slot mappings, and apply variant configurations effectively.

What's the best way to compare merch-card variant schemas?

The best way to compare merch-card variant schemas is to reference the variant registry, which allows you to review detailed field schemas, CSS classes, and slot mappings side-by-side to understand variant differences.

What are the limitations when adding new merch-card variants to the registry?

Adding new merch-card variants is limited by your understanding of web-component architecture and CSS styling. You must correctly define field schemas, CSS classes, and slot mappings to ensure the new variant integrates properly.