Frontend Forge Fe Operations

94TrustedInstructions only

Manage lifecycle, packaging, and publishing for FrontendExtension resources in Kubernetes.

What it does

Frontend Forge Fe Operations provides specialized logic for interacting with FrontendExtension resources inside a Kubernetes cluster. It equips the assistant with the necessary context to navigate the extension lifecycle, from manifest creation and artifact generation to complex publication and removal procedures.

Installing this skill allows the assistant to interpret resource statuses, identify associated batch jobs, and parse configuration data stored in ConfigMaps or Secrets. It shifts the assistant from generic Kubernetes management toward domain-specific tasks involving the frontend-forge extension system.

When it earns its place

Reach for it when…

Use this skill when managing the lifecycle of frontend extensions, specifically during manual deployment updates, troubleshooting failed packaging phases, or performing administrative tasks like unpublishing and cleaning up artifacts.

Look elsewhere when…

This skill is not suitable for handling FrontendIntegration runtime JSBundle creation or other integration layer operations, as it is strictly limited to the FrontendExtension resource and its corresponding build, package, and publication jobs.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • rebuild the package for this frontend extension
  • why is the frontend extension stuck in a failed state
  • unpublish the extension and delete the associated resources
  • locate the artifact configmap for my frontend extension

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch master https://github.com/kubesphere/kubesphere.git /tmp/kubesphere
mkdir -p ~/.claude/skills
cp -r /tmp/kubesphere/skills/frontend-forge-fe-operations ~/.claude/skills/frontend-forge-fe-operations

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/kubesphere/skills/frontend-forge-fe-operations .claude/skills/frontend-forge-fe-operations

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server