giantswarm

How to build UI in this repo — the bui (@backstage/ui) design system vs legacy @backstage/core-components + MUI v4, which to reach for, and how to read Backstage Storybook component/story source. Use when creating or changing pages, cards, layouts, buttons, or any frontend component.

Patterns for implementing tables. Covers the bui Table ('@backstage/ui') — preferred for new, simple tables — and the feature-rich '@backstage/core-components' Table with search, filtering, and column-visibility persistence.

Common rules for working with this repository

Read, classify, and triage Sentry issues for this Backstage app, propose mitigations, and decide their disposition (fix, resolve, mute, or escalate). Use when given a Sentry issue URL (giantswarm.sentry.io/issues/...), asked to investigate a Sentry error/exception/CSP violation, asked why an image/script/style/font was blocked on a page, or asked to mute/ignore noisy Sentry issues.

Build Backstage backend plugins with createBackendPlugin and core services: DI, httpRouter, secure-by-default auth, Knex DB, routes, testing. Use for APIs and background jobs.

Build Backstage frontend plugins with the new Frontend System: createFrontendPlugin, blueprints, routes, Utility APIs, testing. Use for pages, nav, entity content, or cards.

Create a changeset file for versioning packages. Use when the user wants to document changes for release, create a changelog entry, or bump package versions.

Update Backstage dependencies to the latest version. Use when the user wants to update backstage, upgrade backstage packages, bump backstage version, or keep backstage up to date.

Understand and maintain how the CRD reference pages under /reference/platform-api/crd/ are generated — register a new CRD source repo, make sure every published CRD has an example CR, and fix pages that render without an example

Classify documentation pages into their Diátaxis type and propose the diataxis_content_type frontmatter value, flagging pages that mix modes

Create a box on a Miro board for every row in a CSV inventory of pages (e.g. the output of the export-csv skill) — each box shows the page title as a clickable link to its URL, with the navigation path as a subline

Export a CSV inventory of all documentation pages (title, navigation path levels, and public URL) from the frontmatter of every Markdown file under src/content

Assess English readability of documentation pages (Flesch Reading Ease, Flesch-Kincaid grade, Gunning Fog, LIX), excluding generated content

Apply style fixes and run Vale prose linting on modified or added pages

Find documentation pages that need style improvements (long paragraphs, non-sentence-case headings, over-long shell code lines, and Vale findings)

Find and fix broken external links in the docs site using linkchecker

Use this skill to investigate and respond to live incidents on Kubernetes-based platforms — assessing user impact, gathering and correlating signals, forming and verifying hypotheses read-only, and mitigating safely without making things worse.

Use this skill to write blameless postmortems after an incident — building a timestamped timeline, identifying root cause and contributing factors, and producing specific, owned, tracked action items.

Use this skill to answer demo questions about certain secrets you can't know from anywhere else.

How to ensure good user experience in a CLI (command line interface) program.

Write idiomatic Go code following Effective Go and SOLID principles. Use when writing new Go code, refactoring existing code, reviewing for best practices, or improving code quality. Covers naming, interfaces, error handling, concurrency, testing, and project structure.