wix-cli-site-component

Scaffold Wix site components from manifest-driven blueprints with TypeScript and CSS.

25|31|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/wix/skills --skill wix-cli-site-component
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wix-cli-site-component
Source: https://github.com/wix/skills/tree/main/wix-cli/skills/wix-cli-site-component
Command: npx skills add https://github.com/wix/skills --skill wix-cli-site-component

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Wix developers building production-grade site components require a manifest-driven contract and reusable patterns. This Skill provides a blueprint to scaffold and maintain site components within Wix CLI.

Core Features & Use Cases

  • Manifest-driven scaffolding for core files (manifest.json, component.tsx, style.css, types.ts) and a clear extension registration process.
  • Reference-guided development using the provided references to enforce manifest guidelines, TypeScript typings, and CSS variable-driven styling.
  • Use cases include building production-grade Wix site components that integrate with the Wix Editor, enabling drag-and-drop editing, and extending Editor capabilities with a robust extension workflow.

Quick Start

Create a new site component directory with manifest.json and component.tsx following the guidelines, then register the extension using the Wix CLI workflow.

Frequently Asked Questions about wix-cli-site-component

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

FAQPage Schema
How do I build a Wix site component with a manifest.json file?▼

A manifest-driven Wix site component uses manifest.json as a contract to scaffold core files like component.tsx, style.css, and types.ts, ensuring editor integration and consistent production-ready patterns.

How do I register a site component extension using the Wix CLI?▼

To register a site component extension using the Wix CLI, create the component directory with manifest.json and component.tsx, then follow the end-to-end extension workflow to enable drag-and-drop editing in the Wix Editor.

What TypeScript and CSS patterns are required for Wix editor components?▼

Wix editor components require strict TypeScript typings in types.ts and CSS variable-driven styling in style.css, enforced by reference guidelines to maintain production-grade reliability and consistency.

Does the Wix CLI support React and TypeScript for building editor extensions?▼

Yes, the Wix CLI supports React and TypeScript for building editor extensions by generating component.tsx with strict typings and providing a manifest-driven blueprint for robust site component development.

What is the best way to scaffold a production-grade Wix site component?▼

The best way to scaffold a production-grade Wix site component is using a manifest-driven blueprint that generates manifest.json, component.tsx, style.css, and types.ts while enforcing strict TypeScript and CSS guidelines.