- Home
- Skills
- Hyva Themes
- Hyva Ai Tools
- Hyva Theme List
hyva-theme-list_skill
- PHP
38
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill hyva-themes/hyva-ai-tools --skill hyva-theme-list- SKILL.md1.8 KB
Overview
This skill lists all Hyvä theme paths in a Magento 2 project so you can quickly locate Hyvä/Tailwind-based themes. It identifies themes by checking for the Hyvä Tailwind structure alongside a valid Magento theme descriptor. Use it from the project root to get one relative theme path per line, or empty output when none are found.
How this skill works
The script scans common theme locations inside a Magento project (app/design/frontend and vendor) and inspects each candidate directory for two markers: a Tailwind package file under web/tailwind and a theme.xml descriptor. When both files exist, the directory is reported as a Hyvä theme. Output is plain lines with relative paths, suitable for piping into other tools or selection prompts.
When to use it
- You need to find all Hyvä themes installed or developed in a project.
- Preparing to run theme-specific build or Tailwind workflows that require theme paths.
- Other automation skills need a list of Hyvä theme paths to operate on.
- Auditing a project to verify Hyvä adoption or locate third-party Hyvä packages.
- Quickly confirm whether any Hyvä themes are present after dependency changes.
Best practices
- Run the script from the Magento project root so paths are relative and accurate.
- Use the output in pipes or variables for automated workflows (CI, deploy scripts, other skills).
- Verify vendor-installed themes are present by running composer install before discovery.
- Treat results as authoritative only for Hyvä themes that use the web/tailwind layout convention.
Example use cases
- List Hyvä themes before triggering a per-theme Tailwind build step in CI.
- Populate a selection prompt so an extension can ask which Hyvä theme to operate on.
- Scan a codebase to find custom project themes that use Hyvä/Tailwind structure.
- Confirm a newly installed vendor Hyvä theme appears under vendor/ after installation.
FAQ
Execute it from the Magento project root so returned paths are correct and relative to the project.
How does the script identify a Hyvä theme?
It looks for both a web/tailwind package file (Tailwind structure) and a theme.xml Magento descriptor in the same directory.