Skills for the Virto Commerce storefront (vc-frontend): keep a theme fork up to date with upstream, and add a storefront plugin to a backend module. Can make mistakes: review every change before merging.
2 on GitHubby Virto Commercev0.3.1SEE LICENSE IN LICENSEupdated 2 days ago
/
Plugin vc-frontend from marketplace ai-tools in VirtoCommerce/ai-tools. Commands read from the repo's manifest — 2 days ago.
What it installs
Skills (3)
merge-upstream
Use when bringing upstream vc-frontend changes (its dev branch or a release tag) into a theme fork — vc-frontend-next or a customer's storefront theme — or when a long-lived vc-frontend redesign branch has to absorb its base branch and the merge conflicts.
mf-new-plugin
Use when a Virto Commerce backend module that has no storefront plugin yet should ship one (a Module Federation remote for vc-frontend), or when asked to add StorefrontApp/ to a module's *.Web project.
port-upstream-to-fork
Use after merging upstream vc-frontend into a theme fork (vc-frontend-next, a customer theme), or to audit a fork, when the fork has replaced upstream components with its own — a custom header, menu, home page or selector — so upstream fixes to the replaced components never reach users.
Bug lifecycle for Virto Commerce QA — bug filing, autonomous fixing, fix verification, online bug monitoring, self-diagnostics (/vc-self-check), and one renderer for every result comment and report page (/vc-fix:qa-report). Onboarding comes from vc-init (installed with it). Self-contained plugin (10 agents, 16 skills, 7 commands).
PREVIEW — one testing flow per ticket: /vc-test:ticket-context (one gated context bundle, read from Jira or Azure Boards and GitHub or Azure Repos through vc-init's $VC_RUN bridge, or through the host's MCP servers on a host-governed project), /vc-test:qa-test-strategy (floors, gate, an independent verifier), then scenarios that hunt significant bugs, approved at one human point, one agent each, costed per step. /vc-test:init for its own settings. Depends on vc-init and vc-fix. /vc-test:qa-triage-results runs from the plugin; investigation is vc-fix:qa-investigate. /vc-test:qa-design and the ui-ux-expert agent run the visual lane on a Playwright lane the run leaves free.
Onboarding for the Virto Commerce QA plugins — /project-init, the only writer of project-profile.json. Every token it and its dependents need (GitHub, Azure DevOps, Jira) is kept in vc-secrets and reaches a process only through the $VC_RUN bridge, so none sits in a project file. Depends on vc-secrets; Installs on its own; every Virto plugin that reads the profile depends on it.
Collection of example skills demonstrating various capabilities including skill creation, MCP building, visual design, algorithmic art, internal communications, web testing, artifact building, Slack GIFs, and theme styling
Deploy, manage and monitor your Hostinger services directly from Claude Code. The plugin connects Claude to Hostinger's remote MCP server, so you can ship sites and apps, manage domains and DNS, run WordPress and operate VPS servers without leaving your coding environment. There's nothing to install on your machine: no Node.js, no npm, no local server. Key features include one-prompt deployments for static sites, Node.js apps (built on Hostinger), full WordPress site imports, and WordPress plugins and themes, plus static and PHP sites on the Agency Plan. Beyond deployments, Claude can search and register domains, edit DNS records and snapshots, check build logs, and manage mailboxes, online stores, email marketing contacts, subscriptions and orders. It can also control VPS firewalls, snapshots and monitoring. Sign in through your browser (OAuth) on first use, or set a `HOSTINGER_API_TOKEN` from hPanel. How to use: there are no commands to memorize. Describe what you want and Claude picks the right tool or deployment skill. Try "deploy my static site to Hostinger", "deploy this Next.js app to example.com", "create an A record pointing example.com to 1.2.3.4", or "show VPS metrics for the last 24 hours."
Audit a project's npm, PyPI, and Go dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned upstreams, npm publisher concentration, and install scripts
Find UI components and themes, retrieve their code, and use hosted 21st AI when enabled.
1 skill · 1 MCP server
21st-dev/magic-mcp 6,478
Maintain vc-frontend?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.