# FrontendIntegration Operations

Creates, updates and troubleshoots FrontendIntegration resources and the frontend-forge extension.

- Repository: https://github.com/kubesphere/kubesphere (17074 stars)
- Category: DevOps
- License: see repository
- Last updated: 2026-07-15
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kubesphere/kubesphere --skill frontend-forge-fi-operations -g -a claude-code -y`
Codex: `npx skills add kubesphere/kubesphere --skill frontend-forge-fi-operations -g -a codex -y`
Cursor: `npx skills add kubesphere/kubesphere --skill frontend-forge-fi-operations -g -a cursor -y`
Gemini CLI: `npx skills add kubesphere/kubesphere --skill frontend-forge-fi-operations -g -a gemini-cli -y`

## Description

Operate FrontendIntegration resources and the frontend-forge extension. Use when Codex needs to create a FrontendIntegration from FrontendIntegration YAML, update or patch FI lifecycle state, inspect or troubleshoot FI build output, or create, enable, disable, uninstall, and inspect the frontend-forge extension through its InstallPlan and extension resources.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Frontend Forge FI Operations

Operate `FrontendIntegration` resources and the `frontend-forge` extension with `kubectl`.

## When to Use

- Create a `FrontendIntegration` from complete `FrontendIntegration` YAML
- Update, enable, disable, or delete an existing FI
- Inspect FI status, build jobs, `JSBundle`, ConfigMap, manifest, or source-spec annotations
- Troubleshoot FI reconciliation or build output
- Create, enable, disable, uninstall, or inspect the `frontend-forge` extension

## Do Not Use

- Generate new `FrontendIntegration` YAML from natural language
- Manage extensions other than `frontend-forge`
- Assume FI operations are valid before checking extension state
- Use patch as the creation path for a new FI when the user already has YAML

## Preconditions

- `kubectl` must be configured for the target cluster.
- `frontend-forge` extension installation and enabled state are prerequisites for all FI functionality.
- `frontend-forge-controller` exists only after the `frontend-forge` extension is installed.
- `FrontendIntegration` is cluster-scoped. Do not add `-n` when operating on FI resources.

## Read First

- Read [references/extension-management.md](references/extension-management.md) before any FI operation.
- Read [references/lifecycle.md](references/lifecycle.md) for FI create, update, enable, disable, and delete workflows.
- Read [references/inspection.md](references/inspection.md) for FI inspection and troubleshooting.

## Preflight

Always run these checks before any FI create, update, enable, disable, delete, inspect, or troubleshoot flow:

```bash
kubectl get extension frontend-forge
kubectl get installplan frontend-forge -o yaml
```

Only continue to FI operations when:

- the `frontend-forge` extension exists
- the `frontend-forge` InstallPlan exists
- `spec.enabled=true` on the InstallPlan

If the extension is missing or disabled, switch to the extension management workflow first.

## FI Operations

### Create FI From YAML

The rest: https://github.com/kubesphere/kubesphere/blob/HEAD/skills/frontend-forge-fi-operations/SKILL.md