@webiny/mcp 6.1.0-beta.2 → 6.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@webiny/mcp",
-	"version": "6.1.0-beta.2",
+	"version": "6.1.0",
 	"type": "module",
 	"main": "./index.js",
 	"bin": {
@@ -25,7 +25,7 @@
 	"devDependencies": {
 		"@types/lodash": "4.17.24",
 		"@types/ncp": "2.0.8",
-		"@webiny/build-tools": "6.1.0-beta.2",
+		"@webiny/build-tools": "6.1.0",
 		"execa": "5.1.1",
 		"tsx": "4.21.0",
 		"typescript": "5.9.3"
@@ -33,5 +33,5 @@
 	"scripts": {
 		"prepublishOnly": "bash ./prepublishOnly.sh"
 	},
-	"gitHead": "7174b414a55fc1c3f4cf38abab69dba5109e7765"
+	"gitHead": "65e0ac1889b3392c99b8cac6cde508e1e831c715"
 }

package/skills/admin/ui-extensions/SKILL.md

@@ -15,6 +15,8 @@ description: >
 
 Admin extensions customize the Webiny Admin application. There are three main categories: **white-labeling** (logos, titles, theme colors), **custom data list columns** (adding columns to content entry tables), and **custom page-type forms** (custom form fields for Website Builder page types). All are React components registered via `<Admin.Extension>` in `webiny.config.tsx`.
 
+**YOU MUST include the full file path with the `.tsx` extension in every `src` prop.** For example, use `src={"/extensions/MyAdminExtension.tsx"}`, NOT `src={"/extensions/MyAdminExtension"}`. Omitting the file extension will cause a build failure.
+
 ## White-Labeling
 
 ### Theme Colors

package/skills/api/event-handler-pattern/SKILL.md

@@ -265,6 +265,10 @@ export default EntryAfterDeleteEventHandler.createImplementation({
 
 ## Registration
 
+**YOU MUST include the full file path with the `.ts` extension in the `src` prop.** For example, use `src={"@/extensions/my-handler.ts"}`, NOT `src={"@/extensions/my-handler"}`. Omitting the file extension will cause a build failure.
+
+**YOU MUST use `export default` for the `createImplementation()` call** when the file is targeted directly by an Extension `src` prop. Using a named export (`export const Foo = SomeFactory.createImplementation(...)`) will cause a build failure. Named exports are only valid inside files registered via `createFeature`.
+
 ```tsx
 <Api.Extension src={"@/extensions/my-handler.ts"} />
 ```

package/skills/api/graphql-api/SKILL.md

@@ -16,6 +16,10 @@ description: >
 
 Add custom GraphQL queries and mutations using `GraphQLSchemaFactory`. Implement `GraphQLSchemaFactory.Interface`, use the schema builder to add type definitions and resolvers (with per-resolver DI), and export with `GraphQLSchemaFactory.createImplementation()`. Register as `<Api.Extension>`.
 
+**YOU MUST include the full file path with the `.ts` extension in every `src` prop.** For example, use `src={"/extensions/MySchema.ts"}`, NOT `src={"/extensions/MySchema"}`. Omitting the file extension will cause a build failure.
+
+**YOU MUST use `export default` for the `createImplementation()` call** when the file is targeted directly by an Extension `src` prop. Using a named export (`export const Foo = SomeFactory.createImplementation(...)`) will cause a build failure. Named exports are only valid inside files registered via `createFeature`.
+
 ## The GraphQLSchemaFactory Pattern
 
 The `execute` method receives a schema builder and returns it after adding type defs and resolvers.

package/skills/api/use-case-pattern/SKILL.md

@@ -77,6 +77,10 @@ export default SomeUseCase.createImplementation({
 
 ## Registration
 
+**YOU MUST include the full file path with the `.ts` extension in the `src` prop.** For example, use `src={"@/extensions/my-extension.ts"}`, NOT `src={"@/extensions/my-extension"}`. Omitting the file extension will cause a build failure.
+
+**YOU MUST use `export default` for the `createImplementation()` call** when the file is targeted directly by an Extension `src` prop. Using a named export (`export const Foo = SomeFactory.createImplementation(...)`) will cause a build failure. Named exports are only valid inside files registered via `createFeature`.
+
 ```tsx
 // In your app's configuration
 <Api.Extension src={"@/extensions/my-extension.ts"} />

package/skills/cli-extensions/SKILL.md

@@ -56,7 +56,7 @@ export default CliCommandFactory.createImplementation({
 });
 ```
 
-Register in `webiny.config.tsx`:
+Register in `webiny.config.tsx` (**YOU MUST include the `.ts` file extension in the `src` prop** — omitting it will cause a build failure):
 
 ```tsx
 <Cli.Command src={"/extensions/MyCustomCommand.ts"} />

package/skills/content-models/SKILL.md

@@ -43,7 +43,7 @@ class MyModelImpl implements ModelFactory.Interface {
   }
 }
 
-export const MyModel = ModelFactory.createImplementation({
+export default ModelFactory.createImplementation({
   implementation: MyModelImpl,
   dependencies: []
 });
@@ -55,6 +55,10 @@ Register in `webiny.config.tsx`:
 <Api.Extension src={"/extensions/MyModel.ts"} />
 ```
 
+**YOU MUST include the full file path with the `.ts` extension in the `src` prop.** For example, use `src={"/extensions/MyModel.ts"}`, NOT `src={"/extensions/MyModel"}`. Omitting the file extension will cause a build failure.
+
+**YOU MUST use `export default` for the `createImplementation()` call** when the file is targeted directly by an Extension `src` prop. Using a named export (`export const MyModel = ...`) will cause a build failure. Named exports are only valid inside files registered via `createFeature`.
+
 ## Model Configuration Methods
 
 | Method                                        | Purpose                                                                                                                               |
@@ -154,7 +158,7 @@ class ProductCategoryModelImpl implements ModelFactory.Interface {
   }
 }
 
-export const ProductCategoryModel = ModelFactory.createImplementation({
+export default ModelFactory.createImplementation({
   implementation: ProductCategoryModelImpl,
   dependencies: []
 });
@@ -217,7 +221,7 @@ class ProductModelImpl implements ModelFactory.Interface {
   }
 }
 
-export const ProductModel = ModelFactory.createImplementation({
+export default ModelFactory.createImplementation({
   implementation: ProductModelImpl,
   dependencies: []
 });
@@ -284,7 +288,7 @@ class ContactSubmissionModelImpl implements ModelFactory.Interface {
   }
 }
 
-export const ContactSubmissionModel = ModelFactory.createImplementation({
+export default ModelFactory.createImplementation({
   implementation: ContactSubmissionModelImpl,
   dependencies: []
 });
@@ -296,7 +300,7 @@ export const ContactSubmissionModel = ModelFactory.createImplementation({
 Import:       import { ModelFactory } from "webiny/api/cms/model";
 Interface:    ModelFactory.Interface
 Builder:      ModelFactory.Builder
-Export:        ModelFactory.createImplementation({ implementation, dependencies })
+Export:       export default ModelFactory.createImplementation({ implementation, dependencies })
 Register:     <Api.Extension src={"/extensions/MyModel.ts"} />
 Deploy:       yarn webiny deploy api  (or use watch mode)
 ```

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

@@ -22,6 +22,10 @@ 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.
 
+**YOU MUST include the full file path with the `.ts` or `.tsx` extension in every `src` prop.** For example, use `src={"/extensions/lead/src/index.ts"}`, NOT `src={"/extensions/lead"}`. Omitting the file extension will cause a build failure.
+
+**YOU MUST use `export default` for the `createImplementation()` call** when the file is targeted directly by an Extension `src` prop. Using a named export (`export const Foo = SomeFactory.createImplementation(...)`) will cause a build failure. Named exports are only valid inside files registered via `createFeature`.
+
 ```tsx
 // CORRECT — always use entry-point components
 <Api.Extension src={import.meta.dirname + "/api/Extension.js"} />

package/skills/infrastructure-extensions/SKILL.md

@@ -41,7 +41,7 @@ export default CorePulumi.createImplementation({
 });
 ```
 
-Register:
+Register (**YOU MUST include the `.ts` file extension in the `src` prop** — omitting it will cause a build failure):
 
 ```tsx
 <Infra.Core.Pulumi src={"/extensions/MyCorePulumiHandler.ts"} />

package/skills/project-structure/SKILL.md

@@ -99,6 +99,10 @@ export const Extensions = () => {
 | `<Cli.Command src="..." />`                 | Registers a custom CLI command                                                           | `.ts`     |
 | `<Security.ApiKey.AfterUpdate src="..." />` | Registers a security lifecycle hook                                                      | `.ts`     |
 
+**YOU MUST include the full file path with the `.ts` or `.tsx` extension in every `src` prop.** For example, use `src={"/extensions/MyModel.ts"}`, NOT `src={"/extensions/MyModel"}`. Omitting the file extension will cause a build failure.
+
+**YOU MUST use `export default` for the `createImplementation()` call** when the file is targeted directly by an Extension `src` prop. Using a named export (`export const Foo = SomeFactory.createImplementation(...)`) will cause a build failure. Named exports are only valid inside files registered via `createFeature`.
+
 ## Infrastructure Components
 
 Declarative components for configuring AWS infrastructure:

package/skills/webiny-sdk/SKILL.md

@@ -241,7 +241,7 @@ export default ApiKeyFactory.createImplementation({
 });
 ```
 
-Register:
+Register (**YOU MUST include the `.ts` file extension in the `src` prop** — omitting it will cause a build failure):
 
 ```tsx
 <Api.Extension src={"/extensions/MyApiKey.ts"} />