Terminal
Terminal/Skill
Matches a brand or existing website's colors, fonts, imagery, and spacing on Konnect Dev Portal pages.
By Kong
Works with
npx skills add kong/ai-marketplace --skill portal-brandingReproduce a brand or an existing website's look on Dev Portal MDC pages: colors, fonts, imagery, and spacing, through MDC components and page-level styling. Work in MDC page files, locally or in a repo. Do not push destructive changes to a live portal through the Konnect API unless the user explicitly asks.
Ask two or three high-impact questions, each with a default to confirm; do not interrogate:
portal-page-design
toolchain, which uses the Konnect MCP server for verified components, design
tokens, validation, and preview. This skill adds the brand-specific steps below.Aim for a small set of concrete cues, not a pile of screenshots:
Screenshot the source with Playwright at desktop and mobile widths and keep it open beside your work. Match the given source; do not substitute a default brand.
Two levers:
primary token
family derives from the theme's primary color, so setting it once applies the
brand consistently. Change the theme only when the user asks.full-width hero background.For one page, use a component's dedicated appearance props (background-color,
padding, border, border-radius) and inline span styles, for example
[text]{ style="color:#6f28ff;" }. Prefer dedicated props over the catch-all
styles prop, which is only for what props cannot express (a gradient background).
Set fonts portal-wide through the theme so every page matches; for a one-page
exception, set font-family on component style props with a fallback stack.
Run this only with a real portal and a configured token; without them there is no rendered preview and no parity loop, so say so and stop.
Editing an existing page: first screenshot the live page as a "before" at each width, then compare against the "after."
Preview URLs are single-use and time-limited: regenerate only when the MDC changes; once loaded, resize the browser in place to test widths.
The preview uses the target portal's theme, so --kui-*-primary surfaces show
that portal's brand color, not the source's. To judge brand parity, either set
the portal's primary color in the theme first, or use explicit hex on
brand-critical surfaces so the preview is theme-independent.
Contrast: check brand color against its background on buttons and links, and body text against its background. Meet WCAG AA: 4.5:1 for normal text, 3:1 for large text. If the true brand color fails, use it for large surfaces and pick a contrast-safe variant for text.
When an element has no page equivalent, do not drop it silently: offer the closest approximation, or state plainly that the page cannot express the effect.
Stop when tone, colors, fonts, and imagery match and the remaining differences are cosmetic and below the user's fidelity bar. Report residual differences rather than chasing pixels.
--kui-* values from the server's design tokens, not memory; use explicit
hex only for shades beyond the primary palette.portal-page-design for page structure and component choice.technical-writing for page wording.terraform-konnect or kongctl-declarative to encode pages as code.konnect-api-publish or konnect-app-auth when the real issue is API
visibility, publication, or developer application auth.