@webiny/mcp 6.0.0 → 6.1.0-beta.1

package/skills/dependency-injection/SKILL.md

@@ -31,6 +31,7 @@ class MyImplementation implements SomeFactory.Interface {
 
   execute(/* factory-specific params */) {
     this.logger.info("Doing something...");
+    // buildParams.get() returns T | null — always account for null.
     const value = this.buildParams.get<string>("MY_PARAM");
   }
 }
@@ -58,222 +59,7 @@ Key rules:
 | CLI Commands    | `CliCommandFactory`    | `"webiny/cli/command"`   |
 | Pulumi Handlers | `CorePulumi`           | `"webiny/infra/core"`    |
 
-> **Event handlers** use the same `createImplementation` pattern but are not injectable dependencies. See the `lifecycle-events` skill for the full list.
-
-## Injectable Abstractions
-
-Every Abstraction listed below can be used as a constructor dependency or as a base for `createImplementation`. Import from the `"webiny/..."` path shown.
-
-### `webiny/api/build-params`
-
-| Abstraction  | Purpose                  |
-| ------------ | ------------------------ |
-| `BuildParam` | Define a build parameter |
-| `BuildParams` | Access build-time parameters |
-
-### `webiny/api/logger`
-
-| Abstraction | Purpose                          |
-| ----------- | -------------------------------- |
-| `Logger`    | Logging (persists to CloudWatch) |
-
-### `webiny/api/key-value-store`
-
-| Abstraction          | Purpose                        |
-| -------------------- | ------------------------------ |
-| `GlobalKeyValueStore` | Global (cross-tenant) key-value store |
-| `KeyValueStore`      | Tenant-scoped key-value store  |
-
-### `webiny/api/event-publisher`
-
-| Abstraction      | Purpose              |
-| ---------------- | -------------------- |
-| `EventPublisher` | Publish domain events |
-
-### `webiny/api/graphql`
-
-| Abstraction            | Purpose               |
-| ---------------------- | --------------------- |
-| `GraphQLSchemaFactory` | Define GraphQL schemas |
-
-### `webiny/api/tasks`
-
-| Abstraction      | Purpose                |
-| ---------------- | ---------------------- |
-| `TaskService`    | Task management service |
-| `TaskDefinition` | Define a background task |
-
-### `webiny/api/system`
-
-| Abstraction            | Purpose                   |
-| ---------------------- | ------------------------- |
-| `InstallSystemUseCase` | System installation logic |
-
-### `webiny/api/security`
-
-| Abstraction           | Purpose                               |
-| --------------------- | ------------------------------------- |
-| `IdentityContext`     | Current user identity and permissions |
-| `ApiKeyFactory`       | Define custom API key types           |
-| `IdentityProvider`    | Base identity provider abstraction    |
-| `OidcIdentityProvider` | OIDC identity provider               |
-| `JwtIdentityProvider` | JWT identity provider                 |
-| `Authenticator`       | Authentication logic                  |
-| `Authorizer`          | Authorization logic                   |
-
-### `webiny/api/security/api-key`
-
-| Abstraction             | Purpose                     |
-| ----------------------- | --------------------------- |
-| `CreateApiKeyUseCase`   | Create an API key           |
-| `DeleteApiKeyUseCase`   | Delete an API key           |
-| `GetApiKeyUseCase`      | Get API key by ID           |
-| `GetApiKeyByTokenUseCase` | Get API key by token      |
-| `ListApiKeysUseCase`    | List all API keys           |
-| `UpdateApiKeyUseCase`   | Update an API key           |
-| `ApiKeyFactory`         | Define custom API key types |
-
-### `webiny/api/security/role`
-
-| Abstraction       | Purpose        |
-| ----------------- | -------------- |
-| `CreateRoleUseCase` | Create a role |
-| `DeleteRoleUseCase` | Delete a role |
-| `GetRoleUseCase`    | Get role by ID |
-| `ListRolesUseCase`  | List all roles |
-| `UpdateRoleUseCase` | Update a role |
-
-### `webiny/api/security/user`
-
-| Abstraction          | Purpose           |
-| -------------------- | ----------------- |
-| `CreateUserUseCase`  | Create a user     |
-| `DeleteUserUseCase`  | Delete a user     |
-| `UpdateUserUseCase`  | Update a user     |
-| `GetUserUseCase`     | Get user by ID    |
-| `ListUsersUseCase`   | List all users    |
-| `ListUserTeamsUseCase` | List user's teams |
-
-### `webiny/api/tenancy`
-
-| Abstraction              | Purpose                              |
-| ------------------------ | ------------------------------------ |
-| `TenantContext`          | Current tenant information           |
-| `CreateTenantUseCase`    | Create a tenant                      |
-| `CreateTenantRepository` | Tenant creation storage              |
-| `GetTenantByIdUseCase`   | Fetch tenant by ID                   |
-| `UpdateTenantUseCase`    | Update a tenant                      |
-| `UpdateTenantRepository` | Tenant update storage                |
-| `DeleteTenantUseCase`    | Delete a tenant                      |
-| `DeleteTenantRepository` | Tenant deletion storage              |
-| `InstallTenantUseCase`   | Install a tenant                     |
-| `AppInstaller`           | App installation during tenant install |
-
-### `webiny/api/tenant-manager`
-
-| Abstraction            | Purpose                        |
-| ---------------------- | ------------------------------ |
-| `TenantModelExtension` | Extend tenant data model       |
-
-### `webiny/api/cms/entry`
-
-| Abstraction                                         | Purpose                             |
-| --------------------------------------------------- | ----------------------------------- |
-| `CreateEntryUseCase`                                | Create a CMS entry                  |
-| `CreateEntryRevisionFromUseCase`                    | Create entry revision from existing |
-| `DeleteEntryUseCase`                                | Delete an entry                     |
-| `MoveEntryToBinUseCase`                             | Move entry to bin                   |
-| `DeleteEntryRevisionUseCase`                        | Delete a specific revision          |
-| `DeleteMultipleEntriesUseCase`                      | Delete multiple entries             |
-| `MoveEntryUseCase`                                  | Move entry to folder                |
-| `PublishEntryUseCase`                               | Publish an entry                    |
-| `RepublishEntryUseCase`                             | Republish an entry                  |
-| `RestoreEntryFromBinUseCase`                        | Restore entry from bin              |
-| `UnpublishEntryUseCase`                             | Unpublish an entry                  |
-| `UpdateEntryUseCase`                                | Update an entry                     |
-| `UpdateSingletonEntryUseCase`                       | Update a singleton entry            |
-| `GetEntriesByIdsUseCase`                            | Get entries by IDs                  |
-| `GetEntryUseCase`                                   | Get entry by query                  |
-| `GetEntryByIdUseCase`                               | Get entry by revision ID            |
-| `GetLatestEntriesByIdsUseCase`                      | Get latest entries by IDs           |
-| `GetLatestRevisionByEntryIdBaseUseCase`             | Get latest revision (base)          |
-| `GetLatestRevisionByEntryIdUseCase`                 | Get latest revision                 |
-| `GetLatestDeletedRevisionByEntryIdUseCase`          | Get latest deleted revision         |
-| `GetLatestRevisionByEntryIdIncludingDeletedUseCase` | Get latest revision (incl. deleted) |
-| `GetPreviousRevisionByEntryIdBaseUseCase`           | Get previous revision (base)        |
-| `GetPreviousRevisionByEntryIdUseCase`               | Get previous revision               |
-| `GetPublishedEntriesByIdsUseCase`                   | Get published entries by IDs        |
-| `GetPublishedRevisionByEntryIdUseCase`              | Get published revision              |
-| `GetRevisionByIdUseCase`                            | Get revision by ID                  |
-| `GetRevisionsByEntryIdUseCase`                      | Get all revisions of an entry       |
-| `GetSingletonEntryUseCase`                          | Get singleton entry                 |
-| `ListEntriesUseCase`                                | List entries (base)                 |
-| `ListLatestEntriesUseCase`                          | List latest entries                 |
-| `ListPublishedEntriesUseCase`                       | List published entries              |
-| `ListDeletedEntriesUseCase`                         | List deleted entries                |
-| `ValidateEntryUseCase`                              | Validate entry data                 |
-| `CmsWhereMapper`                                    | Map CMS where conditions            |
-| `CmsSortMapper`                                     | Map CMS sort conditions             |
-
-### `webiny/api/cms/model`
-
-| Abstraction           | Purpose                   |
-| --------------------- | ------------------------- |
-| `ModelFactory`        | Define CMS content models |
-| `FieldType`           | Define custom field types |
-| `CreateModelUseCase`  | Create a model            |
-| `CreateModelFromUseCase` | Clone a model          |
-| `UpdateModelUseCase`  | Update a model            |
-| `DeleteModelUseCase`  | Delete a model            |
-| `GetModelUseCase`     | Get model by ID           |
-| `ListModelsUseCase`   | List all models           |
-
-### `webiny/api/cms/group`
-
-| Abstraction          | Purpose         |
-| -------------------- | --------------- |
-| `ModelGroupFactory`  | Define model groups |
-| `CreateGroupUseCase` | Create a group  |
-| `UpdateGroupUseCase` | Update a group  |
-| `DeleteGroupUseCase` | Delete a group  |
-| `ListGroupsUseCase`  | List all groups |
-| `GetGroupUseCase`    | Get group by ID |
-
-### `webiny/api/website-builder/nextjs`
-
-| Abstraction   | Purpose                    |
-| ------------- | -------------------------- |
-| `NextjsConfig` | Configure Next.js integration |
-
-### `webiny/api/website-builder/page`
-
-| Abstraction                     | Purpose                            |
-| ------------------------------- | ---------------------------------- |
-| `CreatePageUseCase`             | Create a page                      |
-| `CreatePageRevisionFromUseCase` | Create page revision from existing |
-| `DeletePageUseCase`             | Delete a page                      |
-| `DuplicatePageUseCase`          | Duplicate a page                   |
-| `GetPageByIdUseCase`            | Get page by ID                     |
-| `GetPageByPathUseCase`          | Get page by path                   |
-| `GetPageRevisionsUseCase`       | Get page revisions                 |
-| `ListPagesUseCase`              | List pages                         |
-| `MovePageUseCase`               | Move a page                        |
-| `PublishPageUseCase`            | Publish a page                     |
-| `UnpublishPageUseCase`          | Unpublish a page                   |
-| `UpdatePageUseCase`             | Update a page                      |
-
-### `webiny/api/website-builder/redirect`
-
-| Abstraction                       | Purpose                    |
-| --------------------------------- | -------------------------- |
-| `CreateRedirectUseCase`           | Create a redirect          |
-| `DeleteRedirectUseCase`           | Delete a redirect          |
-| `GetActiveRedirectsUseCase`       | Get active redirects       |
-| `GetRedirectByIdUseCase`          | Get redirect by ID         |
-| `InvalidateRedirectsCacheUseCase` | Invalidate redirects cache |
-| `ListRedirectsUseCase`            | List redirects             |
-| `MoveRedirectUseCase`             | Move a redirect            |
-| `UpdateRedirectUseCase`           | Update a redirect          |
+> **Event handlers** use the same `createImplementation` pattern but are not injectable dependencies.
 
 ## Examples Across Extension Types
 
@@ -372,9 +158,13 @@ export default CorePulumi.createImplementation({
 3. The `dependencies` array order must match the constructor parameter order.
 4. Read the `abstractions.ts` file in the feature folder to see available methods.
 5. Extensions with no dependencies use `dependencies: []`.
+6. `BuildParams.get<T>(name)` returns `T | null` — always type the receiving property/variable as nullable (e.g. `string | null`) and handle the `null` case.
+7. **BuildParam declarations belong inside the extension's `Extension.tsx`**, not in `webiny.config.tsx`. Expose required params as React props on the extension component so the consumer decides where values come from (see `webiny-full-stack-architect` skill for the full pattern).
 
 ## Related Skills
 
-- `custom-graphql-api` -- DI in GraphQL schema extensions
-- `lifecycle-events` -- DI in lifecycle event handlers
-- `cli-extensions` -- DI in CLI command extensions
+- `webiny-custom-graphql-api` -- DI in GraphQL schema extensions
+- `webiny-cli-extensions` -- DI in CLI command extensions
+- `webiny-full-stack-architect` -- Full-stack extension skeleton and registration pattern
+- `webiny-api-architect` -- API-side architecture using DI
+- `webiny-admin-architect` -- Admin-side architecture using DI

package/skills/full-stack-architect/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: webiny-full-stack-architect
+context: webiny-extensions
+description: >
+  Full-stack extension skeleton and registration pattern. Use this skill when creating
+  an extension that spans both API and Admin — the top-level component with Api.Extension
+  and Admin.Extension entry points, shared domain layer, BuildParam declarations, and
+  package structure. References webiny-api-architect and webiny-admin-architect for layer-specific details.
+---
+
+# Full-Stack Extension Skeleton
+
+## TL;DR
+
+A full-stack extension bundles **API** and **Admin** into a single package with a shared domain layer. The top-level component registers both sides via `<Api.Extension>` and `<Admin.Extension>`, which point to separate entry-point files. Each side follows its own layered architecture pattern — see **webiny-api-architect** and **webiny-admin-architect** skills for details.
+
+## RULE — Extension Entry Points
+
+> **Admin extensions CANNOT be directly mounted in `webiny.config.tsx` or in any child component tree without going through `<Admin.Extension />`.**
+
+The same rule applies to API extensions — they must go through `<Api.Extension />`.
+
+These entry-point components are the **only** way to register code that runs inside the Admin app or the API runtime. They use the `src` prop to point to a file that will be loaded in the correct execution environment (browser for Admin, Lambda for API). Bypassing these entry points will fail at runtime because the Admin and API contexts (DI containers, routers, GraphQL registries, etc.) are not available outside their respective runtimes.
+
+```tsx
+// CORRECT — always use entry-point components
+<Api.Extension src={import.meta.dirname + "/api/Extension.js"} />
+<Admin.Extension src={import.meta.dirname + "/admin/Extension.js"} />
+
+// WRONG — never mount admin/api code directly
+<MyAdminComponent />     // Will not have access to Admin DI container
+<MyApiFeature />         // Will not have access to API DI container
+```
+
+## Package Structure
+
+```
+my-extension/
+├── src/
+│   ├── index.ts                  # Single public export
+│   ├── MyExtension.tsx           # Top-level component (registers Api + Admin)
+│   ├── shared/                   # Shared between API and Admin
+│   │   ├── constants.ts          # Model IDs, permission names, etc.
+│   │   └── types.ts              # Shared types
+│   ├── api/                      # API-side code → see webiny-api-architect skill
+│   │   ├── Extension.ts
+│   │   ├── domain/
+│   │   ├── features/
+│   │   └── graphql/
+│   └── admin/                    # Admin-side code → see webiny-admin-architect skill
+│       ├── Extension.tsx
+│       ├── features/
+│       └── presentation/
+```
+
+## Top-Level Component
+
+The top-level component is the single entry point that consumers use. It registers both the API and Admin extensions:
+
+```tsx
+// src/MyExtension.tsx
+import React from "react";
+import { Api, Admin } from "webiny/extensions";
+
+export const MyExtension = () => {
+  return (
+    <>
+      {/* API extensions — runs in Lambda */}
+      <Api.Extension src={import.meta.dirname + "/api/Extension.js"} />
+
+      {/* Admin extensions — runs in browser */}
+      <Admin.Extension src={import.meta.dirname + "/admin/Extension.js"} />
+    </>
+  );
+};
+```
+
+Conditional rendering can wrap the entry points (e.g., feature flags, config parameters):
+
+```tsx
+<Infra.Env.Is name={"prod"}>
+  <Api.Extension src={import.meta.dirname + "/api/Extension.js"} />
+  <Admin.Extension src={import.meta.dirname + "/admin/Extension.js"} />
+</Infra.Env.Is>
+```
+
+## Shared Domain Layer
+
+The `shared/` directory contains types and value objects used by both API and Admin:
+
+```ts
+// src/shared/constants.ts
+export const MY_MODEL_ID = "myModel";
+
+// src/shared/MyEntity.ts
+export interface MyEntityValues {
+  name: string;
+  status: "active" | "inactive";
+}
+
+export interface MyEntityDto {
+  id: string;
+  values: MyEntityValues;
+}
+
+export class MyEntity {
+  private constructor(private dto: MyEntityDto) {}
+
+  static from(dto: MyEntityDto) {
+    return new MyEntity(dto);
+  }
+
+  get id() {
+    return this.dto.id;
+  }
+
+  get values() {
+    return this.dto.values;
+  }
+}
+```
+
+## Build Parameters
+
+Build parameters pass configuration from `webiny.config.tsx` (build time) into both the API runtime and the Admin app. **A deployed API must NEVER use `process.env` to read configuration.**
+
+**`BuildParam` declarations MUST live inside the extension's top-level component, NOT in `webiny.config.tsx`.** Required parameters are exposed as React props on the extension component.
+
+### Declaring BuildParams
+
+```tsx
+// src/MyExtension.tsx — declares build params as React props
+interface MyExtensionProps {
+  apiEndpoint: string;
+  dashboardUrl: string;
+}
+
+export const MyExtension = ({ apiEndpoint, dashboardUrl }: MyExtensionProps) => {
+  return (
+    <>
+      <Api.BuildParam paramName="MY_API_ENDPOINT" value={apiEndpoint} />
+      <Admin.BuildParam paramName="DASHBOARD_URL" value={dashboardUrl} />
+
+      <Api.Extension src={import.meta.dirname + "/api/Extension.js"} />
+      <Admin.Extension src={import.meta.dirname + "/admin/Extension.js"} />
+    </>
+  );
+};
+```
+
+### Consuming in `webiny.config.tsx`
+
+```tsx
+// webiny.config.tsx — the ONLY place where process.env is read
+<MyExtension
+  apiEndpoint={process.env.MY_API_ENDPOINT || ""}
+  dashboardUrl={process.env.DASHBOARD_URL || ""}
+/>
+```
+
+### Reading BuildParams
+
+- **API side:** Inject `BuildParams` via DI — see **webiny-api-architect** skill
+- **Admin side:** Use `useBuildParams()` hook — see **webiny-admin-architect** skill
+
+## Checklist
+
+1. Create top-level component that uses `<Api.Extension>` and `<Admin.Extension>` — never mount admin/api code directly
+2. Put shared domain models and constants in `shared/`
+3. Declare `<Api.BuildParam>` / `<Admin.BuildParam>` in the top-level component, not in `webiny.config.tsx`
+4. API entry point uses `createFeature` with `register(container)` — see **webiny-api-architect**
+5. Admin entry point is a React component with `<RegisterFeature>` — see **webiny-admin-architect**
+6. Use `.js` extensions in all import paths (ESM modules)
+
+## Quick Reference
+
+```
+Entry point:            <Api.Extension src={...} /> + <Admin.Extension src={...} />
+Shared code:            shared/ directory for domain models, constants, types
+API architecture:       → see webiny-api-architect skill
+Admin architecture:     → see webiny-admin-architect skill
+DI pattern:             → see webiny-dependency-injection skill
+BuildParam declare:     <Api.BuildParam paramName="KEY" value={prop} />
+                        <Admin.BuildParam paramName="KEY" value={prop} />
+BuildParam read (API):  buildParams.get<T>("KEY") via DI (→ webiny-api-architect)
+BuildParam read (Admin): useBuildParams().get<T>("KEY") (→ webiny-admin-architect)
+Import extensions:      Always use .js extensions in import paths (ESM)
+```
+
+## Related Skills
+
+- **webiny-api-architect** — API-side architecture (features, abstractions, container registration)
+- **webiny-admin-architect** — Admin-side architecture (headless + presentation features)
+- **webiny-project-structure** — Extension registration and `webiny.config.tsx`
+- **webiny-dependency-injection** — The `createImplementation` DI pattern and injectable services

package/skills/generated/admin/SKILL.md

@@ -0,0 +1,119 @@
+---
+name: webiny-admin-catalog
+context: webiny-api
+description: >
+  admin — 18 abstractions.
+---
+
+# admin
+
+## How to Use
+
+1. Find the abstraction you need below
+2. Read the source file to get the exact interface and types
+3. Import: `import { Name } from "<importPath>";`
+
+## Abstractions
+
+---
+**Name:** `AdminConfig`
+**Import:** `import { AdminConfig } from "webiny/admin"`
+**Source:** `@webiny/app-admin/config/AdminConfig.tsx`
+
+---
+**Name:** `BaseError`
+**Import:** `import { BaseError } from "webiny/admin"`
+**Source:** `@webiny/feature/admin/index.ts`
+
+---
+**Name:** `BuildParam`
+**Import:** `import { BuildParam } from "webiny/admin"`
+**Source:** `@webiny/app-admin/features/buildParams/index.ts`
+
+---
+**Name:** `BuildParams`
+**Import:** `import { BuildParams } from "webiny/admin"`
+**Source:** `@webiny/app-admin/features/buildParams/index.ts`
+
+---
+**Name:** `createAbstraction`
+**Import:** `import { createAbstraction } from "webiny/admin"`
+**Source:** `@webiny/feature/admin/index.ts`
+
+---
+**Name:** `createFeature`
+**Import:** `import { createFeature } from "webiny/admin"`
+**Source:** `@webiny/feature/admin/index.ts`
+
+---
+**Name:** `createHasPermission`
+**Import:** `import { createHasPermission } from "webiny/admin"`
+**Source:** `@webiny/app-admin/permissions/index.ts`
+
+---
+**Name:** `createPermissionSchema`
+**Import:** `import { createPermissionSchema } from "webiny/admin"`
+**Source:** `@webiny/app-admin/permissions/index.ts`
+
+---
+**Name:** `createProvider`
+**Import:** `import { createProvider } from "webiny/admin"`
+**Source:** `@webiny/app/core/createProvider.tsx`
+**Description:** Creates a Higher Order Component which wraps the entire app content.
+This is mostly useful for adding React Context providers.
+
+---
+**Name:** `createProviderPlugin`
+**Import:** `import { createProviderPlugin } from "webiny/admin"`
+**Source:** `@webiny/app/core/createProviderPlugin.tsx`
+**Description:** Creates a component, which, when mounted, will register an app provider.
+This is particularly useful for wrapping the entire app with custom React Context providers.
+For more information, visit https://www.webiny.com/docs/admin-area/basics/framework.
+
+---
+**Name:** `createUsePermissions`
+**Import:** `import { createUsePermissions } from "webiny/admin"`
+**Source:** `@webiny/app-admin/permissions/index.ts`
+
+---
+**Name:** `DevToolsSection`
+**Import:** `import { DevToolsSection } from "webiny/admin"`
+**Source:** `@webiny/app-admin/components/index.ts`
+**Description:** Registers a named section in the Webiny DevTools extension.
+Renders nothing — purely a data registration side-effect.
+
+When the component unmounts (e.g., route change), the section
+is automatically removed from DevTools.
+
+---
+**Name:** `NetworkErrorEventHandler`
+**Import:** `import { NetworkErrorEventHandler } from "webiny/admin"`
+**Source:** `@webiny/app/errors/index.ts`
+
+---
+**Name:** `Plugin`
+**Import:** `import { Plugin } from "webiny/admin"`
+**Source:** `@webiny/app/core/Plugin.tsx`
+
+---
+**Name:** `Provider`
+**Import:** `import { Provider } from "webiny/admin"`
+**Source:** `@webiny/app/core/Provider.tsx`
+**Description:** Register a new React context provider.
+
+---
+**Name:** `RegisterFeature`
+**Import:** `import { RegisterFeature } from "webiny/admin"`
+**Source:** `@webiny/app-admin/components/RegisterFeature.tsx`
+
+---
+**Name:** `Routes`
+**Import:** `import { Routes } from "webiny/admin"`
+**Source:** `@webiny/app-admin/routes.ts`
+
+---
+**Name:** `useFeature`
+**Import:** `import { useFeature } from "webiny/admin"`
+**Source:** `@webiny/app/shared/di/useFeature.ts`
+
+---

package/skills/generated/admin/aco/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: webiny-admin-aco-catalog
+context: webiny-api
+description: >
+  admin/aco — 2 abstractions.
+---
+
+# admin/aco
+
+## How to Use
+
+1. Find the abstraction you need below
+2. Read the source file to get the exact interface and types
+3. Import: `import { Name } from "<importPath>";`
+
+## Abstractions
+
+---
+**Name:** `useNavigateFolder`
+**Import:** `import { useNavigateFolder } from "webiny/admin/aco"`
+**Source:** `@webiny/app-aco/hooks/useNavigateFolder.ts`
+
+---
+**Name:** `useRecords`
+**Import:** `import { useRecords } from "webiny/admin/aco"`
+**Source:** `@webiny/app-aco/hooks/useRecords.ts`
+
+---

package/skills/generated/admin/build-params/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: webiny-admin-build-params-catalog
+context: webiny-api
+description: >
+  admin/build-params — 3 abstractions.
+---
+
+# admin/build-params
+
+## How to Use
+
+1. Find the abstraction you need below
+2. Read the source file to get the exact interface and types
+3. Import: `import { Name } from "<importPath>";`
+
+## Abstractions
+
+---
+**Name:** `BuildParam`
+**Import:** `import { BuildParam } from "webiny/admin/build-params"`
+**Source:** `@webiny/app-admin/features/buildParams/index.ts`
+
+---
+**Name:** `BuildParams`
+**Import:** `import { BuildParams } from "webiny/admin/build-params"`
+**Source:** `@webiny/app-admin/features/buildParams/index.ts`
+
+---
+**Name:** `useBuildParams`
+**Import:** `import { useBuildParams } from "webiny/admin/build-params"`
+**Source:** `@webiny/app-admin/presentation/buildParams/useBuildParams.ts`
+
+---