mcpbeat

Frontend Integration Yaml

kubesphere/frontend-integration-yaml

Generate canonical FrontendIntegration YAML from a simplified single-menu authoring model for frontend-forge.

7k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
17017
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kubesphere/kubesphere --skill frontend-integration-yaml

The instruction itself

8 sections, as written by the author

Frontend Integration YAML

Generate submit-ready FrontendIntegration YAML from a simplified authoring model with one menu and one or more pages.

When to Use

  • generate FrontendIntegration YAML
  • create a quick integration YAML from a CRD
  • create an iframe based FrontendIntegration YAML
  • convert simplified single-menu config into canonical YAML

Do Not Use

  • troubleshooting existing FrontendIntegration resources
  • managing enable/disable/delete lifecycle
  • inspecting JSBundle, Job, controller, or status flows
  • editing manifest generation rules
  • handling multi-menu authoring models

Required Inputs

Ask the user instead of guessing when any of these are missing:

  • metadata.name
  • menu.displayName
  • menu.placements[]
  • at least one page in pages[]
  • for crdTable: group, version, scope, names.plural
  • for iframe: key and iframe.src

Authoring Model

Use the simplified single-menu model as input to the generator:

  • top-level metadata
  • top-level spec for optional passthrough fields
  • top-level menu
  • top-level pages

Do not author canonical spec.menus[] by hand.

Workflow

  • Extract the simplified authoring model.
  • Fill only safe defaults.
  • Keep the model in single-menu form.
  • Run scripts/generate_frontend_integration.py.
  • Return the generated canonical YAML.

Rules

  • Treat the generator script as the source of truth.
  • Do not manually reconstruct canonical YAML when the generator is available.
  • Always output canonical kind: FrontendIntegration.
  • Always expand menu.placements[] into spec.menus[].
  • Always derive children from pages[].
  • If any placement is workspace, force all crdTable.scope values to Namespaced.
  • Default menu.icon to GridDuotone when it is omitted.
  • Do not add runtime-managed metadata unless explicitly requested.

Output

  • Return the generated YAML first, unless explanation is requested.
  • Prefer a single yaml code block.
  • After the YAML, always output this exact guidance line:

FrontendIntegration YAML has been generated. Reply 'apply' to deploy it directly.

How to use it

Copy the folder

Take kubesphere/frontend-integration-yaml from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.