Update to Vercel

{
  "name": "microfrontends",
  "description": "Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 105
    },
    {
      "relative_path": "references/configuration.md",
      "size_in_bytes": 7270
    },
    {
      "relative_path": "references/local-development.md",
      "size_in_bytes": 5861
    },
    {
      "relative_path": "references/managing-microfrontends.md",
      "size_in_bytes": 7608
    },
    {
      "relative_path": "references/path-routing.md",
      "size_in_bytes": 6140
    },
    {
      "relative_path": "references/security.md",
      "size_in_bytes": 4189
    },
    {
      "relative_path": "references/troubleshooting.md",
      "size_in_bytes": 8202
    }
  ],
  "skill_md_contents": "---\nname: microfrontends\ndescription: Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.\nmetadata:\n  priority: 7\n  docs:\n    - \"https://vercel.com/docs/microfrontends\"\n  pathPatterns:\n    - 'microfrontends.json'\n    - 'microfrontends.jsonc'\n    - 'apps/*/microfrontends.json'\n    - 'apps/*/microfrontends.jsonc'\n  bashPatterns:\n    - '\\bvercel\\s+microfrontends\\b'\n    - '\\bvercel\\s+mf\\b'\n    - '\\bnpm\\s+(install|i|add)\\s+[^\\n]*@vercel/microfrontends\\b'\n    - '\\bpnpm\\s+(install|i|add)\\s+[^\\n]*@vercel/microfrontends\\b'\n    - '\\bbun\\s+(install|i|add)\\s+[^\\n]*@vercel/microfrontends\\b'\n    - '\\byarn\\s+add\\s+[^\\n]*@vercel/microfrontends\\b'\n  importPatterns:\n    - '@vercel/microfrontends'\n---\n\n# Vercel Microfrontends\nSplit a large application into independently deployable units that render as one cohesive app. Vercel handles routing on its global network using `microfrontends.json`.\n\n**Core concepts:** default app (has `microfrontends.json`, serves unmatched requests) · child apps (have `routing` path patterns) · asset prefix (prevents static-asset collisions) · independent deployments.\n\n**Frameworks:** Next.js (App Router + Pages Router), SvelteKit, React Router, Vite — all via `@vercel/microfrontends`.\n\n**CLI (`vercel microfrontends` / `vercel mf`):**\n- `create-group` — create a new group; interactive by default, or fully non-interactive with `--non-interactive` (options: `--name`, `--project` (repeatable), `--default-app`, `--default-route`, `--project-default-route` (repeatable, format: `<project>=<route>`, required for each non-default project in non-interactive mode), `--yes` to skip confirmation prompt); note: `--non-interactive` is blocked if adding the projects would exceed the free tier limit — the user must confirm billing changes interactively\n- `add-to-group` — add the current project to an existing group; requires interactive terminal (options: `--group`, `--default-route`)\n- `remove-from-group` — remove the current project from its group; requires interactive terminal (option: `--yes` skips project-link prompt only)\n- `delete-group` — delete a group and all its settings, irreversible; requires interactive terminal (option: `--group` to pre-select group)\n- `inspect-group` — retrieve group metadata (project names, frameworks, git repos, root dirs); useful for automating setup (options: `--group`, `--format=json`, `--config-file-name`)\n- `pull` — pull remote `microfrontends.json` for local development (option: `--dpl`)\n- `microfrontends proxy` — local dev proxy · `microfrontends port` — print auto-assigned port\n\n## Finding Detailed Information\n\nThis skill includes detailed reference docs in the `references/` directory. **Do not read all references upfront.** Instead, search or grep the relevant file when the user asks about a specific topic:\n\n| Topic | Reference file |\n|---|---|\n| Getting started, quickstart, framework setup, `microfrontends.json` schema, fields, naming, examples | `references/configuration.md` |\n| Path expressions, asset prefixes, flag-controlled routing, middleware | `references/path-routing.md` |\n| Local proxy setup, polyrepo config, Turborepo, ports, deployment protection | `references/local-development.md` |\n| Inspecting groups (`inspect-group`), adding/removing projects, fallback environments, navigation, observability | `references/managing-microfrontends.md` |\n| Testing utilities (`validateMiddlewareConfig`, `validateRouting`, etc.), debug headers, common issues | `references/troubleshooting.md` |\n| Deployment protection, Vercel Firewall, WAF rules for microfrontends | `references/security.md` |\n\nWhen the user asks about a specific topic, use grep or search over the relevant reference file to find the answer without loading all references into context.\n"
}