Kong
- 59 skills
- 0 followers
- 11 hours ago last updated
- ▌ Theme Creation · kong bundleUse this skill whenever the user wants to create, add, author, or scaffold a new theme for the @kong/design-tokens package — including phrases like "add a new theme", "create a new theme", "make a dark/light theme", "I need a new theme for Kongponents", "a new data-kui-theme", "match this screenshot/mockup", "make our theme look like this site/URL", "here are our brand colors", "port/emulate an existing theme", "make a theme like One Dark Pro", or "match this VS Code/editor/terminal theme". Also use it if the user wants to modify how an existing theme relates to design tokens (semantic vs component tokens, color aliases/palettes) as part of building a new one, or supplies a screenshot, mockup, reference URL, brand guideline, or the name of an existing published theme (editor, terminal, or otherwise) as the basis for a theme's look. Make sure to trigger this even if the user doesn't say "design-tokens", "Style Dictionary", or "theme" explicitly — a request to reskin, rebrand, or restyle the product to match so
- ▌ Convert Cypress To Vitest Component · kongConvert Cypress component tests (*.cy.ts) to Vitest Browser Mode tests (*.browser.spec.ts) in the Kongponents library. Use this whenever the user asks to convert, migrate, port, or rewrite component tests from Cypress to Vitest, names one or more component folders under src/components to convert ("do KBadge and KAlert next", "convert KTable"), asks to continue or resume the Cypress-to-Vitest migration, or mentions Vitest browser mode for component tests. Use it even when the user never says "Cypress" or "Vitest" — a request to migrate, port, or redo the tests for a named Kongponent is this skill.
- ▌ CLI HTML Preview · kongRender proposed CLI/terminal output (colors, tables, status lines, TUI reports) as a standalone HTML file and open it in the browser, so the user can review a styling/output design before it is implemented. Use whenever the user asks to "show me what the CLI output would look like", "preview the colored output", "mock up the terminal output in a browser", or wants to eyeball a color theme / table layout before code is written.
- ▌ Component Docs · kong bundleAuthor or update a component doc in the Docusaurus site (packages/insomnia-component-docs) for a component in the shared library. Use when adding a new component to src/basic-components, changing a component's props/variants, or when asked to document/update docs for a component.
- ▌ Fix Test CLI CI · kongDebug failures from the test-cli.yml workflow locally. Use when insomnia-inso bundle tests fail in CI, especially node-vs-electron dependency/runtime mismatches.
- ▌ Fix Scripting Feature · kong bundleDebug and fix issues in Insomnia's pre-request/after-response/test scripting feature (the pm/insomnia API surface). Use when scripts throw sandbox violations, timeouts, module import errors, or produce wrong request/response/variable mutations.
- ▌ Agentic Workflows · kongRoute gh-aw workflow design/create/debug/upgrade requests to the right prompts.
- ▌ Kongctl Extension Builder · kong bundleScaffold and maintain kongctl CLI extensions. Use when a user wants to create a script or Go extension, define extension command paths, use the kongctl Go SDK helper, test install/link workflows, or debug extension context handling.
- ▌ Kuma To Mesh · kongConvert 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.
- ▌ Release Changelog · kongUse this skill when the user runs "/release-changelog", asks to "generate a release changelog", "write release PR description", "build preview links for release", or wants to summarize all docs changed in a release PR as a grouped list of links.
- ▌ Third Party Plugin · kong bundleCreate complete documentation for a new third-party Kong Gateway plugin on developer.konghq.com. Use this skill whenever the user asks to document, write, or create a new third-party Kong Gateway plugin page, including index.md, schema.json, or example YAML files. Also use it when someone shares a plugin schema (Lua or JSON), a GitHub repo, or vendor plugin assets and asks for help turning them into developer.konghq.com documentation. Trigger even if the user only says "write docs for my plugin", "add a plugin page", or "document this schema".
- ▌ Kongctl New Command · kongSyncs 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').
- ▌ Kong Identity How To · kong bundleWrite 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.
- ▌ Dcgw Terraform How To · kong bundleWrite 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.
- ▌ AI Gateway Migration Review · kongReviews AI Gateway documentation files for correctness during the v1 → v2 migration. Use this skill whenever you need to audit or fix AI Gateway docs for migration issues — whether reviewing specific files or all AI Gateway files across how-tos, landing pages, and reference pages. Triggers on requests like "review this ai-gateway file", "check my migration", "audit ai-gateway docs for v2", "find v1 references in ai-gateway pages", "update this file for AI Gateway v2", or any time someone is working on AI Gateway content under app/_how-tos/ai-gateway, app/_landing-pages/ai-gateway, or app/ai-gateway.
- ▌ Go Code Review · kong bundleAdversarial Go code review for .go files, go.mod/go.sum changes, and PRs with Go code. Orchestrates an adversarial reviewer over the diff against 100+ common Go mistakes, then audits the findings with a findings auditor before reporting. Use when reviewing Go changes, a Go PR, or assessing Go implementation quality.
- ▌ Ksai Do · kongDo one named piece of work on a pull request that already exists - fix a failing check, add a missing test, make a change somebody asked for in a comment - and report what you did as a JSON manifest. One request, one run, one commit. Use when a ksai implement flow hands you a request and, when CI is red, the failing checks and their logs.
- ▌ Lua Code Review · kong bundleAdversarial Lua code review for .lua files, rockspecs, Test::Nginx .t suites, and PRs with OpenResty or Kong Gateway plugin code. Orchestrates an adversarial reviewer over the diff against a catalog of Lua, LuaJIT, OpenResty and Kong PDK mistakes, then audits the findings with a findings auditor before reporting. Use when reviewing Lua changes, an OpenResty or Kong plugin PR, or assessing Lua implementation quality.
- ▌ Vue Code Review · kong bundleAdversarial Vue code review for .vue single-file components, Vue/Nuxt .ts/.js/.mjs files, package.json changes, and PRs containing Vue code. Orchestrates an adversarial reviewer over the diff against a Vue / Nuxt / TypeScript mistakes catalog (reactivity, component contracts, Pinia, Nuxt SSR, real test coverage), then audits the findings with a findings auditor before reporting. Use whenever reviewing Vue or Nuxt changes, a Vue/Nuxt PR, a component or composable, or assessing Vue/TypeScript implementation quality — even if the request just says "review this component" without naming Vue.
- ▌ Ksai Fix · kongAnswer the open review threads on a pull request - change the code where the review is right, say so where it is not, and report one reply per thread as a JSON manifest. One commit for the whole pass. Use when a ksai implement flow hands you a list of unresolved review threads on a pull request.
- ▌ Ksai Plan · kongPlan a GitHub issue or a Jira ticket as a plan document an approver reviews, holding an ordered list of independently committable steps for a CI flow that implements one step per run. Reads the ticket and the repo, sizes each step to one commit with a clear completion test, writes the document, and reports the run as a JSON manifest. Use at the start of a ksai implement run, before any code is written.
- ▌ Ksai Step · kongImplement exactly one named step of a planned GitHub issue, run the repo's quality gates, adversarially review and adversarially test it, and commit it locally as a single commit. Resumable - each CI run does one step and reports out as a JSON manifest. Use when a ksai implement flow hands you one step title from a plan produced by ksai-plan.
- ▌ Ksai Build · kongImplement a whole small GitHub issue in one run, run the repo's quality gates, adversarially review and adversarially test it, and commit it locally as a few coherent commits. Not resumable - one run does the whole issue and reports out as a JSON manifest. Use when a ksai implement flow sized an issue as small enough to skip planning.
- ▌ Nestjs Code Review · kong bundleAdversarial NestJS code review for Kong backend services - .ts files in NestJS repos, package.json changes touching @nestjs/* deps, and PRs containing NestJS code. Orchestrates an adversarial reviewer over the diff against a NestJS/TypeScript mistakes catalog (DI scopes, pipeline order, validation, transactions, cross-request state, security, real test coverage) plus Kong conventions (shared @kong/* libraries, RLS, AIP/problem+json, gRPC error discrimination), then audits the findings with a findings auditor before reporting. Use whenever reviewing NestJS changes, a NestJS PR, or a controller/service/module - even if the request just says "review this service" without naming NestJS - but ONLY when the repo is a NestJS project (@nestjs/core or @nestjs/common in package.json, a nest-cli.json, or @Module/@Controller/@Injectable decorators present). NOT for Vue/Nuxt or other frontend TypeScript, and not for plain TypeScript or Node.js projects without NestJS - route those to vue-code-review or default-code-review
- ▌ Default Code Review · kong bundleAdversarial fallback code review for any language or framework that has no dedicated kreview skill. Orchestrates an adversarial reviewer over the diff against language-agnostic axes (correctness, edge cases, concurrency, failure paths, security, data integrity, hidden assumptions, tests that don't test), then audits the findings with a findings auditor before reporting. Use when reviewing a PR or diff whose primary language/framework has no matching kreview skill (e.g. Rust, Python, Terraform, YAML/config-only, shell) — this is the catch-all, not a per-language specialist.
- ▌ Typescript Code Review · kong bundleAdversarial TypeScript and JavaScript code review for .ts/.tsx/.mts/.cts and .js/.jsx/.mjs/.cjs files, tsconfig.json and package.json changes, and PRs containing TypeScript or Node code. Orchestrates an adversarial reviewer over the diff against a catalog of 80 TypeScript and JavaScript mistakes (type escapes that become runtime bugs, floating and misused promises, races across an await, resource and listener lifetime, unvalidated boundaries, injection and prototype pollution, tests that cannot fail), then audits the findings with a findings auditor before reporting. Use when reviewing TypeScript or JavaScript changes, a Node or browser PR, or assessing TypeScript implementation quality. Vue, Nuxt and NestJS files have reviewers of their own.
- ▌
- ▌ Volcano Sdk · kongUse for any request to build, create, extend, debug, or deploy an app, website, backend, API, or function using Volcano, even when the user does not mention the SDK. Entrypoint and router; always pair with volcano-platform and the applicable domain skills.
- ▌ Volcano Auth · kongUse for Volcano authentication and identity work including user accounts, email or password sign-up and sign-in, OAuth, sessions, anonymous users, password recovery, and private or per-user data.
- ▌ Volcano Nextjs · kongUse for Next.js on Volcano and for web apps, pages, dashboards, boards, galleries, full-stack UIs, public HTTP routes, redirects, webhook ingress, middleware, API routes, server actions, and client or server SDK separation.
- ▌ Install Volcano · kongInstall, upgrade, or set up the Volcano CLI. Use this whenever a task needs the volcano CLI and `which volcano` hasn't been confirmed yet, even if the user never says "install" (e.g. "build me a todo API using volcano").
- ▌ Volcano Storage · kongUse for file and object storage in Volcano apps, including uploads, downloads, photo galleries, file sharing, buckets, ownership-aware paths, public or private files, visibility, and resumable uploads.
- ▌ Volcano Database · kongUse whenever a Volcano app stores or persists data, including CRUD, records, per-user data, migrations, RLS, todos, chat messages, polls, analytics, counters, click tracking, CMS content, feature flags, and leaderboards.
- ▌ Volcano Platform · kongUse for every Volcano project build, scaffold, local run, test, or deploy. Covers canonical project shape, Functions and frontends, migrations, volcano-config.yaml, environment variables, shared code, and the build and deploy workflow. Pair with volcano-sdk for application features.
- ▌ Volcano Realtime · kongUse for realtime or live updates in Volcano apps, including collaborative boards, chat, presence and online users, live polls and results, leaderboards, Postgres changes, broadcast, WebSockets, and connection lifecycle.
- ▌ Volcano Functions · kongUse for Volcano server-side Functions and privileged or secret-bearing logic, including function invocation, generators such as QR codes or PDFs, outbound third-party APIs, orchestration, scheduled processing, and file or image processing.
- ▌ Volcano Typescript · kongCanonical TypeScript type definitions for the Volcano SDK: User, Session, AuthResponse, QueryBuilder, StorageObject, Realtime types, Function invocation generics, OAuth providers, middleware types, and utility types.
- ▌ Volcano Error Handling · kongReusable error handling patterns for Volcano SDK apps: centralized error dispatcher with action enum, useApiCall React hook for loading/error/data state, retry with exponential backoff, retry with toast notifications, and cross-domain error message catalog.
- ▌ Deck Gateway · kong bundleManage Kong Gateway entities with decK. Use for `deck gateway` state files, validate/diff/sync/dump workflows, OpenAPI-derived Gateway config, or GitOps-style Gateway entity repos. Do not use for Konnect platform resources or HCL/kongctl repos.
- ▌ Kongctl Query · kong bundleUse when the user wants read-only `kongctl` queries against Konnect: prove auth or scope, discover the right `get` path, list or fetch resources, or shape JSON/YAML output. Do not use for `kongctl` plan/apply/sync or declarative authoring.
- ▌ Portal Branding · kongReplicate a brand or existing website's design on Kong Konnect Dev Portal pages. Use to match colors, fonts, imagery, and spacing through MDC components and page-level styling for visual parity.
- ▌ Konnect App Auth · kong bundleUse when Konnect Dev Portal APIs are published but blocked by application auth strategy, registration, approval, or app-credential flow issues; not for Portal sign-in/SSO or basic API publication.
- ▌ Technical Writing · kongWrite task-oriented developer documentation and Dev Portal page copy in plain, active-voice prose with clear, scannable structure. Use when authoring or editing technical docs, API guides, and page content.
- ▌ Terraform Konnect · kong bundleUse when a repo already manages Konnect in Terraform or the user explicitly wants HCL, Terraform import, or plan/apply for Konnect resources; not for `decK`/`kongctl` repos, generic Terraform-only troubleshooting, or domain-first Konnect diagnosis.
- ▌ Konnect AI Gateway · kong bundleOperate Konnect AI Gateway request flow, provider/model routing, AI Proxy behavior, prompt/response controls, and LLM analytics. Use when the issue is inside AI Gateway, not generic prompt engineering, provider SDK debugging, or non-AI Gateway rollout.
- ▌ Portal Page Design · kongStructure and compose Kong Konnect Dev Portal pages with MDC components like heroes, cards, columns, tabbed panels, callouts, and expandable sections. Use for page layout, section design, and component choice. Not for documentation writing or editing.
- ▌ Kongctl Declarative · kong bundleUse for `kongctl`-managed Konnect declarative repos: author YAML, model APIs from OpenAPI, and run plan/diff/apply/sync/delete/adopt workflows or CI/CD. Do not use for read-only inspection, exact `get` syntax, or non-`kongctl` toolchains.
- ▌ Konnect API Catalog · kong bundleDiagnose and shape Konnect API Catalog APIs, versions, specs, implementations, and API packages before publication. Use when Catalog readiness is the question, not when the real owner is Dev Portal publication, app auth, or gateway delivery.
- ▌ Konnect API Publish · kong bundleOperate Konnect API publication from managed API through Catalog and Dev Portal. Use when an API should be visible but the missing link is Catalog readiness, portal publication, or audience scoping. Not for Catalog modeling or post-publication app auth.
- ▌ Kong Skill Authoring · kongCreate or refactor a skill in this repo. Use when deciding extend-versus-create, classifying domain/tool/router ownership, tightening a description, or reviewing a skill package against repo policy. Not for the product workflow itself.
- ▌ Konnect Access Scope · kong bundleTroubleshoot Konnect operator access and visibility. Use when a user cannot authenticate, cannot see or edit a Konnect resource, may be in the wrong region, org, or team, or needs help with scoped roles or IdP-managed access. Not for Dev Portal app auth.
- ▌ Konnect Monetization · kong bundleModel and validate Konnect usage-based billing across meters, features, plans, rate cards, and invoices. Use when turning a pricing model into billing entities or checking allowance and overage math. Not for AI Gateway cost analytics or API Catalog packaging.
- ▌ Konnect Event Gateway · kong bundleUse when diagnosing Konnect Event Gateway request flow across listeners, hostname mapping, virtual/backend clusters, auth, and policy evaluation. Exclude generic gateway health, org access control, and declarative implementation after the failing hop is known.
- ▌ Gateway Plugin Datakit · kong bundleUse when designing or debugging Kong DataKit plugin flows, including node selection, DAG wiring, jq transforms, cache or vault usage, and phase-specific request or response orchestration. Do not use for generic decK, Terraform, or Konnect workflow questions.
- ▌ Konnect Gateway Triage · kong bundleUse when triaging Konnect Gateway control-plane and data-plane failures such as disconnected planes, missing rollout, or wrong environment slices; separate attachment, network, live-state drift, and traffic-path failures before handing off fixes.
- ▌ Terraform Kong Gateway · kong bundleUse when editing or reviewing Terraform that manages self-managed Kong Gateway Admin API entities with the official `kong/kong-gateway` provider; not for Konnect resources, decK-native Gateway GitOps, or gateway troubleshooting before tool choice.
- ▌ Konnect Platform Router · kongRoute broad or ambiguous Konnect requests to the first owning specialist skill. Use when multiple Konnect surfaces are involved or the right owner is unclear, not when the user already named a specific workflow, toolchain, or non-Konnect task.
- ▌ Konnect Observability Triage · kong bundleDiagnose missing, partial, delayed, or mis-scoped Konnect observability data across analytics, Explorer, and Debugger. Use when the question is dataset, scope, or telemetry visibility, not pure gateway health or operator-access troubleshooting.
- ▌ Konnect Control Plane Bootstrap · kong bundleBootstrap new Konnect Gateway control planes. Use for first-run topology, hosted versus self-hosted data planes, region/name/ownership choices, or moving from quickstart setup to durable management. Not for runtime triage or post-bootstrap Gateway config.