Index of every page on this site: llms.txt
All skills
wix avatar

/wix-app

@e2bc48e official
by Wix.comwix/skills40 stars
42
Run it yourself

Build and review Wix CLI app extensions — dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, context providers, function libraries, lightbox (popup) behavior, page onLoad contexts, backend APIs, backend events, service plugins, data collections, and App Market readiness. Use when building ANY feature or extension for a Wix CLI app or preparing a Wix app for App Market review. Triggers on: add, build, create, implement, help me, dashboard, widget, plugin, backend, API, event, collection, embedded script, service plugin, Editor React component, context provider, function library, onLoad, on page load, checkout, shipping, tax, discount, SPI, CMS, schema, tracking, popup, lightbox, admin panel, menu item, modal, validate, test, verify, register extension, App Market, app review, submission readiness.

Use this Skill: https://skilld.dev/gh/wix/skills/wix-app

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencescontext-providervertical-contextsblogcategory-item.md

≈720 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Blog context: @wix/blog/context/category-item

Read Importing a Context in Code first. Import only the hook, from @wix/blog/context/category-item.

CategoryItemContextProvider

Supplies one post category, injected per repeater cell, to its children.

import { CategoryItemContextProvider } from '@wix/blog/context/category-item';
  • Parameters: __0: CategoryItemContextProviderProps
  • Returns: ReactNode

useCategoryItemContext

Nullable rather than throwing: the hook runs for every element inside the repeater cell, including on the editor stage before the cell is populated.

import { useCategoryItemContext } from '@wix/blog/context/category-item';
  • Parameters: none
  • Returns: PostCategoryItem \| null
Returned types
CategoryItemContextProviderProps
Property Type Description
categoryData PostCategoryItem | undefined The current item of the postCategories array, injected by the platform per repeater cell (the Post context manifest's contextImplementor.propKey). Absent on the editor's unbound template cell — children then render over a null context, matching the Post Item provider; this provider has no standalone fetch path.
children ReactNode
PostCategoryItem
Property Type Description
_id string The category's ID.
label string The category's name, as plain text.
itemCategoryLabel RichText The category's name, as rich text: text is the plain text, and html is an HTML paragraph.
itemCategoryLink Link | undefined Link to the blog page that lists the category's posts, with its URL in href. undefined when the site has no such page.
categoryItem { label: string; slug: string; } The category's name and slug.
RichText
Property Type Description
text string The original rich text content.
html string
linkList Link[]
Link
Property Type Description
href string | undefined The link URL. For partial links (see pageRole), this is the router prefix (e.g. https://www.my-site.com/prefix) rather than a fully resolved URL.
target LinkTarget | undefined Where this link should open. - '_self' — opens in the same page. - '_blank' — opens in a new tab.
rel string | undefined
pageRole string | undefined Page role identifier. Present only on partial links, where only the router prefix is known and the full URL format is owned by the Router/App. Applications can use such links in functions to resolve the complete URL at runtime (e.g. for binding links). Resolved links will not have this field.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warningstoday4 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill provides a comprehensive environment and set of tools for building Wix CLI app extensions. It includes detailed instructions, API references, and local utility scripts for development tasks like SDK lookup and accessibility auditing. All operations and dependencies are standard for the Wix developer platform.

  • Sockettoday

    1 alert: gptAnomaly

  • Snyktoday

    Risk: MEDIUM · 1 issue

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e2bc48e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 6 days ago
compatibility
requires `@wix/cli` >= 1.1.192.

README badge

README badge for wix/skills/wix-app

Builds dashboard pages, modals, plugins, custom widgets, Editor React components, backend APIs, events, service plugins, and data collections for Wix CLI apps. Provides decision logic, API patterns, and validation workflows; scaffolding is owned by the Wix CLI via `wix generate --params`.

Generated from the current SKILL.md.

What extension types does this skill cover?
All Wix CLI app extension types: dashboard pages, modals, plugins, menu plugins, custom element widgets, Editor React components, site plugins, embedded scripts, backend APIs, backend events, service plugins, and data collections.
Does this skill scaffold the extension files for me?
The Wix CLI owns scaffolding via `wix generate --params` for all extension types except Backend API. This skill provides decision logic, API guidance, and business-logic patterns to fill in the generated stubs. Backend API files must be created manually.
What Wix CLI version is required?
The skill requires @wix/cli >= 1.1.192.
Do I need to create a Data Collection extension for app-specific data?
Yes, if you're saving or persisting app-specific data, managing domain entities in a dashboard, or running a service plugin that reads app-configured data. The skill infers this automatically—you don't need to explicitly request it.
Does this skill cover Wix Stores API usage?
Yes. When using any Wix Stores API (products, inventory, orders), the skill requires dual V1/V3 catalog support and references the Stores Versioning guide for module selection and field mapping.

Generated from the current SKILL.md. These answers refresh after source changes.