hyva-cms-components-dump

Merge Hyvä CMS components.json files from active Magento modules into one JSON object.

Updated Mar 12, 2026

Search Tags:#components #debug #merge #modules #cms #hyva #magento

Ready to run

npx skills add https://github.com/Happy-Horizon/cursor-marketplace --skill hyva-cms-components-dump-happy-horizon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hyva-cms-components-dump
Source: https://github.com/Happy-Horizon/cursor-marketplace/tree/main/plugins/hyva-ai-tools/skills/hyva-cms-components-dump
Command: npx skills add https://github.com/Happy-Horizon/cursor-marketplace --skill hyva-cms-components-dump-happy-horizon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Locates and consolidates Hyvä CMS component definitions across active Magento modules by scanning module configuration and component files, then outputs a unified view for discovery and debugging.

Core Features & Use Cases

Locate all components.json files from Hyvä CMS modules in active Magento installations and emit a merged definitions object.
View the complete list of available CMS components and detect definition conflicts or missing entries across modules.
Use in development and integration tasks to validate module component wiring and to generate a single source of truth for component definitions.

Quick Start

From the Magento project root, run php <skill_path>/scripts/dump_cms_components.php to generate the merged CMS components.

Frequently Asked Questions about hyva-cms-components-dump

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

FAQPage Schema

How do I list all Hyvä CMS components in a Magento installation?▼

You can consolidate Hyvä CMS component definitions by running a PHP script from the Magento project root. It scans active modules across app/code and vendor paths, merging all components.json files into a single unified JSON object for review.

How does merging Hyvä CMS components.json files work across modules?▼

Merging Hyvä CMS components.json files works by scanning active Magento modules across app/code and vendor directories. It maps paths via etc/module.xml, preserving module load order to output a single unified JSON object containing all CMS component definitions.

Can I detect missing or conflicting CMS component definitions in Magento?▼

Yes, you can detect missing or conflicting CMS component definitions in Magento by generating a consolidated JSON view. This unified output serves as a single source of truth to validate module component wiring and spot definition conflicts across modules.

Do I need to run this from the Magento project root to find Hyvä components?▼

Yes, you need to run the dump script from the Magento project root. This ensures the script can properly access and scan active modules across both app/code and vendor directories to successfully locate and merge Hyvä CMS components.

What is the best way to generate a single source of truth for Hyvä CMS component definitions?▼

The best way to generate a single source of truth for Hyvä CMS component definitions is using a dump script that merges all components.json files from active Magento modules. It preserves module load order and outputs a unified JSON object for downstream analysis.