From zephyr
Use when the user asks about zephyr:dependencies, hosts/remotes, Module Federation build order, remote resolution, cross-bundler remotes, or monorepo MF on Zephyr.
How this skill is triggered — by the user, by Claude, or both
Slash command
/zephyr:zephyr-module-federationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for Zephyr's Module Federation workflow: host/remote setup, `zephyr:dependencies`, resolution behavior, build order, and cross-bundler examples.
Use this skill for Zephyr's Module Federation workflow: host/remote setup, zephyr:dependencies, resolution behavior, build order, and cross-bundler examples.
Module Federation is the pattern where a host app loads code from separately built remote apps at runtime.
Zephyr does not replace normal Module Federation config; it adds deploy-time dependency resolution and routing on top of the host/remote setup.
Use this skill when the user needs help wiring, resolving, or deploying hosts/remotes. Use zephyr-core when the question is mostly about general Zephyr setup, version URLs, tags/environments, or public env vars.
../zephyr-core/SKILL.md.zephyr:dependencies.workspace:* is the most important Zephyr-specific dev workflow for coordinated branch/user/CI resolution.package.json, MF config, and dependency declarations.references/setup-patterns.md for host/remote config shapes.references/remote-resolution.md for zephyr:dependencies, selectors, and workspace:*.references/examples.md for concrete file paths and snippets.references/gotchas.md for build order, naming, and mixed-bundler edge cases.references/docs-map.md.https://docs.zephyr-cloud.iohttps://github.com/ZephyrCloudIO/zephyr-exampleshttps://docs.zephyr-cloud.iohttps://docs.zephyr-cloud.io/<path>.mdhttps://docs.zephyr-cloud.io/llms.txtzephyr:dependencies as a replacement for MF config; it complements it.npx claudepluginhub zephyrcloudio/skills --plugin zephyrGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.