Webiny Skill Generator

Generates per-category catalog JSON files from the webiny npm package's public API. Each catalog lists all UseCase and EventHandler abstractions in a category with their resolved source file paths. LLMs read source files on demand for exact, up-to-date types — no enrichment phase needed.

How It Works

bash
1yarn generate-skills

The script:

1. Discovers all EventHandler and UseCase exports from packages/webiny
2. Resolves the actual source file path for each export via ts-morph
3. Writes one catalog JSON per category to skills/catalogs/

That's it. No skeletons, no enrichment, no templates.

Output

skills/
├── catalogs/
│   ├── api-cms.json           # 82 entries
│   ├── api-security.json      # 37 entries
│   ├── api-website-builder.json
│   ├── api-tenancy.json
│   ├── api-file-manager.json
│   ├── api-aco.json
│   ├── api-scheduler.json
│   └── api-system.json
└── patterns/
    ├── use-case.md            # Generic UseCase pattern doc
    └── event-handler.md       # Generic EventHandler pattern doc

Each catalog entry looks like:

json
1{
2  "className": "CreateTenantUseCase",
3  "importPath": "webiny/api/tenancy",
4  "type": "use-case",
5  "typeLabel": "UseCase",
6  "humanName": "Create Tenant",
7  "entity": "Tenant",
8  "operation": "create",
9  "sourceFilePath": "packages/api-core/src/features/tenancy/CreateTenant/index.ts",
10  "description": "Programmatically create tenant."
11}

How LLMs Use Catalogs

1. Find the right abstraction: Read the catalog JSON for the relevant category
2. Read the pattern doc: skills/patterns/use-case.md or skills/patterns/event-handler.md
3. Resolve types on demand: Read the sourceFilePath from the catalog entry to get exact interfaces, payloads, and error types
4. Generate code: Use the pattern + resolved types to write the extension

This ensures types are always current — no stale snapshots.

CLI Options

bash
1# Full regeneration
2yarn generate-skills
3
4# Verbose output
5yarn generate-skills --verbose
6
7# Check discovered exports without writing files
8yarn generate-skills --check
9
10# Only process a specific category
11yarn generate-skills --category api/cms
12
13# Only process a specific plugin type
14yarn generate-skills --plugin event-handler

Release Workflow

1. Run yarn generate-skills after a platform release
2. Commit the updated catalog files
3. That's it — no enrichment step needed

Adding a New Abstraction Type

To support a new pattern (e.g., classes ending in Middleware):

1. Create a new plugin in scripts/generateSkills/src/plugins/ implementing the AbstractionPlugin interface
2. Register it in scripts/generateSkills/src/plugins/index.ts
3. Run the pipeline — new entries appear in catalogs automatically