메뉴
Convert a Kuma documentation page from the kuma-website repo into a Kong Mesh documentation page for developer.konghq.com. Use when converting, migrating, or porting a Kuma doc to Kong Mesh.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/Kong/developer.konghq.com --skill kuma-to-mesh명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
Write or revise Terraform-based Dedicated Cloud Gateways (DCGW) how-to guides for developer.konghq.com. Use this skill any time someone asks to draft, write, create, update, or revise a Dedicated Cloud Gateways how-to that provisions resources with Terraform, including Azure VNet peering, Azure Virtual WAN, AWS VPC peering or Transit Gateway, GCP VPC peering, managed cache, custom domains, private DNS, or any new DCGW Terraform integration. Always use this skill before writing any DCGW Terraform how-to content, even if the request seems straightforward. Also use it when an engineer or PM shares raw HCL, a Konnect API request, or cloud provider configs and asks for help turning them into a DCGW Terraform how-to.
Syncs kongctl reference docs after a release: creates pages for new commands, removes pages for dropped commands, and updates navigation indexes and redirects. Trigger when the user runs '/kongctl-new-command', shares a 'Sync kongctl Releases' PR, asks to update pages under app/kongctl/, or asks to add, create, or document a new kongctl command (e.g. 'add docs for kongctl roar', 'create a page for the new kongctl command', 'update app/kongctl with the new command').
Write or revise Kong Identity how-to guides for developer.konghq.com. Use this skill any time someone asks to draft, write, create, update, or revise a how-to guide that involves Kong Identity, including OIDC, Upstream OAuth, OAuth Introspection, Event Gateway OAuth, Dev Portal DCR, or any new Kong Identity integration. Always use this skill before writing any Kong Identity how-to content, even if the request seems straightforward. Also use it when an engineer or PM shares a draft or raw configs and asks for help turning them into Kong Identity how-to documentation.
SOC 직업 분류 기준
| name | kuma-to-mesh |
| description | Convert a Kuma documentation page from the kuma-website repo into a Kong Mesh documentation page for developer.konghq.com. Use when converting, migrating, or porting a Kuma doc to Kong Mesh. |
| argument-hint | <path-to-kuma-source-file> |
| allowed-tools | Read Write Edit Bash |
The arguments are: <path-to-kuma-source-file>. Parse it as the first space-separated token of $ARGUMENTS.
Convert the Kuma documentation file into a Kong Mesh documentation page.
/developer.konghq.com/app/mesh//developer.konghq.com/app/_how-tos/mesh/developer.konghq.com/app/_mesh_policies/developer.konghq.com/app/_data/kuma_to_mesh/config.yamlRead the conversion config. Search the pages: list for an entry whose path matches the source file (relative to the kuma-website root, e.g. ).
app/_src/introduction/architecture.mdIf a config entry is found, use its values as the authoritative source for:
titledescriptionurl (determines the target filename)related_resourcesmin_versiontagsRead the Kuma source file. Note its existing frontmatter fields (title, description, keywords, content_type, category) and full body content. Identify the type of content: if it contains mostly step-by-step instructions, it's a how-to. If the category is policy, it's a policy. Otherwise it's a reference.
url field.
url: '/mesh/architecture/' → target file is architecture.mddeveloper.konghq.com/app/mesh/<filename>.mddeveloper.konghq.com/app/_how-tos/mesh/<filename>.mddeveloper.konghq.com/app/_mesh_policies/<policy_name>/index.md and add developer.konghq.com/app/_mesh_policies/<policy_name>/examples/<example_name>.yamlCheck whether the target file already exists. If it does, show the user the existing content and ask whether to overwrite before proceeding.
Do NOT add anything to the /mesh/policies/ folder. For example, /mesh/policies/mutual-tls.md should be migrated to /mesh/mutual-tls.md.
If the URL changes as a result, set a permalink. For example:
permalink: /mesh/policies/mutual-tls/
Construct the frontmatter block with these rules:
Always include (from config entry if available, otherwise derive):
title: "<title with 'Kuma' replaced by {{site.mesh_product_name}}>"
description: "<description with 'Kuma' replaced by {{site.mesh_product_name}}>"
products:
- mesh
breadcrumbs:
- /mesh/
Include if the page is reference content:
content_type: reference
layout: reference
permalink: <config url when the desired URL does not match the default URL from app/mesh/<filename>.md>
Include if the page is a policy:
name: <CRD kind, usually plural, e.g. MeshFaultInjections or MeshAccessLogs>
content_type: plugin
type: policy
icon: policy.svg
Do NOT include breadcrumbs or layout for policies.
Include if the page is a how-to guide:
content_type: how_to
permalink: <based on the original url>
works_on:
- on-prem # always for Universal/VM guides; add konnect if the guide applies there too
tldr:
q: <question form of the page title, e.g. "How do I deploy X?">
a: <one-sentence summary of what the reader achieves by following this guide>
prereqs:
inline:
- title: <prerequisite title>
content: |
<prerequisite content — see Step 5g for how to extract this from the body>
cleanup:
inline:
- title: <cleanup title>
content: |
<cleanup steps — see Step 5g for how to extract this from the body>
Omit prereqs or cleanup if the source page has no corresponding section.
Omit works_on only if scope cannot be determined.
The tldr.a value should complete the sentence "By the end of this guide, you will ...".
Include if available:
tags:
- <converted from source `keywords:` field, plus any tags from config entry, and remove any tags not present in app/_data/schemas/frontmatter/tags.json>
related_resources:
- text: ...
url: /mesh/...
min_version:
mesh: 'X.Y' # from config entry only
Do NOT carry over: keywords, category, the original content_type, or any Kuma build-system fields.
Title/description "Kuma" replacement rules:
Kuma (the product) with {{site.mesh_product_name}}kumactl, kuma-cp, kuma-dp, kuma.io, kumahqApply the following transformations to the Markdown body in order:
Replace all occurrences of /docs/{{ page.release }}/ and /docs/{{page.release}}/ with relative links to the page.
kuma → kong-meshIn any URL (inside markdown links (...) or HTML href "..."), where the URL starts with / or #:
kuma with kong-meshkumactl, kuma-cp, kuma-dp, kuma.io, kumahqlinks: section)Apply these verbatim substitutions anywhere they appear in link targets:
/install/ → /mesh/#install-kong-mesh/enterprise/ → /mesh//community/ → https://konghq.com/community/policies/ → /mesh/policies//features/ → /mesh/enterprise/When replacing relative links, check against https://developer.konghq.com/ that the URL doesn't return a 404 and that the anchor exists.
In body text (not inside code blocks, YAML examples, or annotations):
Kuma (the product name) with {{site.mesh_product_name}}kumactl, kuma-cp, kuma-dp, kuma.io, kumahq, and any kuma.io/ annotation strings{% if_version %} blocks){% if_version %} block only applies to versions older than the min_version, (for example, {% if_version lte:2.5.x %} when min_version is 2.9), remove the content.{% if_version %} block applies to the min_version and later versions, (for example, {% if_version gte:2.6.x %} when min_version is 2.9), keep the content and remove the version gating.In other cases, do NOT attempt to automatically resolve version gates. Instead:
{% if_version %} / {% endif_version %} tags in placeReplace {:.tip} and {:.note} with {:.info}.
Replace {% tip %} and {% warning %} blocks with {:.info} and {:.warning}, for example:
{% tip %}
If you want to configure version, ciphers or per service permissive / strict mode check out [`MeshTLS`](/mesh/policies/meshtls)
{% endtip %}
Should be replaced with:
{:.info}
> If you want to configure version, ciphers or per service permissive / strict mode check out [`MeshTLS`](/mesh/policies/meshtls)
Replace {% tabs %} with {% navtabs %} and {% tab %} with {% navtab %}
Replace any markdown table with the {% table %} block, for example:
{% table %}
columns:
- title: Name
key: name
- title: Description
key: description
rows:
- name: Field name
description: Field description
{% endtable %}
Prerequisites section: If the body contains a ## Prerequisites section, move its content into the prereqs.inline frontmatter field and remove the heading from the body. Each top-level list item in that section becomes a separate - title: / content: | entry.
Cleanup section: If the body contains a ## Cleanup section, move its content (including any code blocks) into the cleanup.inline frontmatter field and remove the heading from the body. Use a content: | block scalar — code fences inside YAML block scalars are preserved correctly.
Section heading style: Rewrite section headings to use imperative mood:
{% mermaid %} conversionFor each image reference in the body ( or <img src="...">) that appears to be an architectural or flow diagram:
https://raw.githubusercontent.com/kumahq/kuma-website/master/app/assets/images/<filename>) and inspect it visually to understand its content.{% mermaid %} block using the most appropriate diagram type:
graph LR / graph TD) — component relationships, request paths{% mermaid %} block.Example output format:
{% mermaid %}
graph LR
DPP(Data plane proxy) -->|XDS| CP(Control plane)
CP -->|config| DB[(PostgreSQL)]
{% endmermaid %}
{% mermaid %} blocks (already converted){% schema_viewer %}, {% policy_yaml %} tags{:.warning}, {:.info} callouts``` fences)kuma.io/ annotation strings inside YAML/code examplesWrite the fully transformed content to the target file path.
If the page is a policy, extract examples from the source file and write each one to developer.konghq.com/app/_mesh_policies/<policy_name>/examples/<example_name>.yaml using this format:
title: 'Human readable title'
description: 'What this example does.'
weight: 900
namespace: kong-mesh-demo
config:
type: <CRD kind>
name: <example-name>
mesh: default
spec:
...
Read the written file and suggest prose improvements. Do not apply them automatically — list them for the user to review. Use .github/copilot-instructions.md for reference.
Present the suggestions as a numbered list with the original text and proposed replacement.
Remove the entry for the converted file from the conversion config.
Show a summary with:
Kuma → {{site.mesh_product_name}} replacements"){% if_version %} blocks that were left in place/mesh/ equivalent known)related_resources (if config had none and source had none)min_version was set or needs to be determined