/webiny-skill-creator

name: webiny-skill-creator
description: >
  Generate, refresh, and maintain Webiny MCP server skills from source documentation and codebase.
  Use this skill when you need to create new Webiny skills, update existing skills after framework
  changes, regenerate the entire skill library, or create a skill for a specific Webiny feature.
  Trigger this whenever someone says "create a skill", "update skills", "refresh skills",
  "add a new skill for X", or "regenerate the skill library". This is the meta-skill that
  produces all other Webiny MCP skills.

Webiny Skill Creator

This skill generates and maintains the set of skills served by the Webiny MCP server. It operates in two modes:

1. **Full regeneration** -- Reads all source documentation and the codebase, then generates/updates the complete skill library. 2. **Single skill creation** -- Creates or updates one skill for a specific Webiny feature.

Skill Output Format

Every skill lives in its own folder as `<skill-name>/SKILL.md` with YAML frontmatter. The MCP server recursively scans for `SKILL.md` files and auto-generates the catalog from front-matter metadata -- no README index is needed.

webiny/my-skills/
├── <skill-name>/
│   └── SKILL.md
├── <skill-name>/
│   └── SKILL.md
└── ...

Skill File Structure

Each `<skill-name>/SKILL.md` file follows this template:

---
name: webiny-<topic>
description: >
  What this skill covers and when to use it.
  Be specific about trigger phrases and developer intents.
  Err on the side of being "pushy" -- describe scenarios broadly
  so the MCP server surfaces this skill when relevant.
---

# Title

## TL;DR

One paragraph actionable summary.

## Pattern / Core Concept

The main code pattern with a generic template.

## Reference Tables

Tables for methods, properties, types, imports.

## Full Examples

2-3 complete, working code examples showing real use cases.

## Quick Reference

Import paths, interfaces, registration, deploy commands.

## Related Skills

Links to other skills that complement this one.

Writing Guidelines

These guidelines ensure skills are effective when served by the MCP server to AI agents:

1. **TL;DR first** -- Every skill starts with a one-paragraph actionable summary. An agent should be able to read just this and know if the skill is relevant.

2. **Generic pattern before examples** -- Show the abstract pattern template first, then concrete examples. This helps agents generalize rather than copy-paste.

3. **Complete, working code** -- Every code block must be copy-paste ready. Include all imports, class definitions, and export statements. Never show partial snippets that require guessing.

4. **Reference tables for APIs** -- Use markdown tables for method signatures, field types, validators, injectable services, etc. Tables are dense and scannable.

5. **Exact import paths** -- Always show the full import path. Webiny uses feature-based imports (e.g., `"webiny/api/cms/model"` not `"@webiny/api-headless-cms"`). Getting the import wrong breaks everything.

6. **The universal DI pattern** -- Every API extension uses `createImplementation({ implementation, dependencies })`. Reinforce this in every skill that covers an API extension type.

7. **Registration in webiny.config.tsx** -- Always show how to register the extension. Include the JSX element and the `src` path convention.

8. **Deploy command** -- Always end with which deploy command to run (`yarn webiny deploy api`, `admin`, or `core`).

9. **Related skills** -- Cross-link to complementary skills. Developers rarely need just one skill.

10. **Description frontmatter** -- The `description` field is the primary trigger mechanism. Include:

• What the skill does
• Specific developer intents that should trigger it
• Keywords and phrases developers might use
• Be slightly aggressive about claiming relevance

Source Documentation

When generating or updating skills, read from these sources in priority order:

1. Existing Skills (`<root>/packages/mcp/src/skills/`)

Read the current skills first to understand what exists and what needs updating.

2. Learn Webiny Lessons (`learn-webiny/content/lessons/`)

The tutorial content organized by topic:

| Directory | Topics Covered | | ------------------------- | -------------------------------------------------------------------------------------- | | `foundation/` | Webiny overview, framework, apps, multi-tenancy, infrastructure | | `developing-with-webiny/` | Project structure, extensions, SDK overview, local dev, debugging, white-labeling | | `headless-cms/` | Content models, versioning, lifecycle events, reading/writing data, list customization | | `website-builder/` | Setup, editor components, theming, CMS integration | | `getting-started/` | Installation, CLI overview, deployment |

3. Legacy Skills (`skills-bak/`)

The previous generation of skills. Good reference for structure and patterns but may have outdated imports or APIs.

4. Webiny Codebase (`webiny/`)

The actual development instance:

| Path | What to Look At | | ------------------- | -------------------------------------------------------------- | | `webiny.config.tsx` | Real extension registration examples | | `extensions/` | Working extension implementations | | `ai-context/` | Core features reference with import paths and type definitions | | `packages/` | Package source code for verifying APIs |

5. Webiny AI Context (`webiny/ai-context/`)

Contains `core-features-reference.md` with verified import paths and type definitions for:

• Core