skills.rest
webiny
webinyOFFICIAL
Explore all skills by this author →
Website𝕏@WebinyCMSGitHub

webiny-admin-catalog

Catalogs Webiny admin framework abstractions with import paths and source references.

8.0k|673|Updated Jan 9, 2018
Search Tags:#catalog#cms#admin#Dependency Injection#webiny#import paths#reAct
One-click install
npx skills add https://github.com/webiny/webiny-js --skill webiny-admin-catalog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: webiny-admin-catalog
Source: https://github.com/webiny/webiny-js/tree/main/skills/user-skills/generated/admin
Command: npx skills add https://github.com/webiny/webiny-js --skill webiny-admin-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers extending the Webiny admin application struggle to discover which React components, hooks, features, and DI abstractions exist and where to import them from, forcing manual searches across a large monorepo.

Core Features & Use Cases

  • Abstraction Discovery: Lists 28 core admin abstractions (AdminConfig, createFeature, createProvider, Plugin, Routes, Notifications, and more) with exact import statements from the webiny/admin entry point.
  • Source Mapping: Maps every abstraction to its source file in packages like @webiny/app-admin and @webiny/feature so developers can read exact interfaces and types before use.
  • Use Case: When building a custom admin extension, a developer needs to register a React context provider and a command palette command; this catalog points directly to createProviderPlugin, Command, and CommandPalettePresenter with their import paths.

Quick Start

Ask the assistant to find the right Webiny admin abstraction and import path for registering a feature or provider in your extension.

Frequently Asked Questions about webiny-admin-catalog

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

FAQPage Schema
How do I find the right Webiny admin abstraction to import?▼

Browse the catalog entries grouped by name, each showing the exact import statement from webiny/admin and the source file path. Read the referenced source file to confirm the interface and types before importing.

How do I register a React context provider in a Webiny admin app?▼

Use createProvider or createProviderPlugin from webiny/admin. createProvider builds a higher-order component wrapping app content, while createProviderPlugin registers the provider when the component mounts.

What is the difference between createFeature and createAbstraction in Webiny?▼

Both are exported from webiny/admin via @webiny/feature. createAbstraction defines a DI abstraction contract, while createFeature registers a feature implementation against that abstraction in the admin app.

Does the Webiny admin catalog include UI components?▼

The core admin catalog covers framework-level abstractions like Plugin, Routes, and Notifications. UI components such as Button, Dialog, and DataTable are cataloged separately under the webiny/admin/ui entry point.

Why must I read the source file before using a cataloged abstraction?▼

The catalog lists names, imports, and source locations but not full type signatures. Reading the source file in packages like @webiny/app-admin ensures you use the exact interface, generics, and required parameters.

Related Skills

Explore More Software Engineering Skills→
fycd2006fycd2006

admin-developer

Build and wire admin features with React views, DI, and MobX.

Community
Advanced
ShopifyShopify
491

shopify-polaris-admin-extensions

Generate Shopify admin extensions with Polaris components and validation scripts.

Official
Intermediate
hulusi-tunchulusi-tunc
3

shadcn-ui

Provide ready-made shadcn/ui component patterns for React projects.

Community
Advanced
featbitfeatbit
11

featbit-documentation

Return official FeatBit documentation URLs from docs.featbit.co with brief rationales.

Official
Intermediate