entur

Build React applications with Entur Linje @entur/* component packages. Use when the user is installing, importing, or using any @entur/* package, asking about Entur React components, Entur tokens, Entur CSS variables, Entur design system in a development context, or building web UI that should follow Entur's component library. Trigger for any code task involving @entur/button, @entur/form, @entur/tokens, @entur/typography, @entur/travel, or any other @entur/* package — even if the user just describes wanting to build something that fits Entur's look and feel in React.

Build accessible Entur web applications that comply with WCAG 2.1 and Norwegian universell utforming (UU) requirements. Use when the user is working on accessibility, asking about WCAG, universell utforming, screen readers, keyboard navigation, focus management, color contrast, aria attributes, semantic HTML, or Norwegian IKT accessibility regulation. Also trigger when building @entur/* applications that need to meet legal compliance requirements — all Entur digital products must comply with WCAG 2.1. Use even if the user just says "make this accessible" or "is this accessible" without mentioning WCAG by name.

Apply Entur's visual identity correctly in designs, presentations, data visualizations, and web UI. Use when the user asks about Entur colors, Entur branding, Entur typography, Entur data visualization, creating charts or graphs for Entur, making a presentation that looks like Entur, building a branded web page or document for Entur, or anything that should follow Entur's visual identity. Trigger even if the user doesn't say "design system" — if they mention Entur and are making something visual, this skill applies.

Entur Linje design system — use when building anything with @entur/* React components, Entur branding, Entur tokens, Entur colors, Entur typography, Entur data visualization, Entur accessibility, or universell utforming (UU). Trigger for any question or task involving the Entur design system, Entur's visual identity, Entur transport UI, or compliance with Norwegian accessibility law (WCAG). Use this skill whenever the user mentions Entur in a design, development, or content context — even if they don't specifically say "design system."

Use when reading, updating, or creating documentation for design system components. Triggers on tasks involving Sanity content, component docs, documentation pages, or the documentation website. Use this skill whenever the user mentions docs, component documentation, Sanity content, the documentation website, or wants to update descriptions for components in the design system.

Complete rules for writing conceptual Guides (guides/) in the Nordic NeTEx Profile. Covers section structure, tone, length, formatting, and cross-referencing. Self-contained — no external files needed.

Complete rules for writing Object documentation (objects/) and Frame documentation (frames/) in the Nordic NeTEx Profile. Includes section templates, table format, structure overview notation, and naming conventions. Self-contained — no external files needed.

Visual conventions, formatting rules, diagram palettes, callout syntax, text style, and quality checklist for all Nordic NeTEx Profile documentation. Self-contained — no external files needed.

Use this skill when creating, reviewing, or updating documentation for the Nordic NeTEx Profile. Routes to the correct sub-skill based on what you're writing (object, frame, guide). Start here for orientation.

Use this skill any time the user asks a question about the Nordic NeTEx Profile — elements, frames, objects, cardinality, references, profile differences (MIN vs NP), XML structure, or how to model a specific transport scenario. Always consult the ontology and the specific Table_/Description_ files before answering. Do not answer from general NeTEx knowledge; the Nordic Profile is a constrained subset and details matter.

Skriv, forklar og debug BigQuery-spørringer mot Tavla sitt Firestore-datasett i GCP. Bruk denne skillen når noen spør om statistikk, analyse, telling, aktivitetsdata, innholdsanalyse eller migrasjonsvalidering av Tavla-boards, mapper eller brukere i BigQuery. Trigger også ved spørsmål som "hvor mange boards har X", "finn boards som mangler Y", "boards som ikke har vært aktive", "boards med linje-ID Z", eller generelt når noen vil hente innsikt fra Firestore-eksportdata eller trenger SQL mot Tavla-databasen.

Triage av Dependabot-PRer, sikkerhetsvarsler og CodeQL-funn for Tavla. Bruk når noen på Tavla-teamet er på dependency-vakt og skal vurdere åpne Dependabot-PRer, klassifisere risiko, vurdere CVE-utnyttbarhet, eller skrive triage-notater. Trigger også ved omtale av "dependency-vakt", "avhengighetsoppdatering", "sikkerhetsvarsel", "Dependabot", "mandagsbrief", "ukens pakker", "pakkeansvarlig". Brukes også for å skrive ukens dependency-brief. Skillen forklarer alltid hvorfor — målet er å bygge kompetanse i teamet over tid, ikke bare gjøre vurderingen.

Provides architectural context about the Tavla product — a Norwegian public transit departure board system. Use this skill whenever working on Tavla code, discussing Tavla repositories, debugging Tavla issues, or planning features for either the admin application or the departure board displays. Trigger on any mention of "tavla", "tavla-admin", "tavla-visning", departure boards, or when navigating either of the two Tavla repositories. Also trigger when questions arise about the Firebase setup, Firestore collections, Firebase Functions, or backend infrastructure used by the product.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Bootstrap a new Entur application from scratch. Generates self-service manifests, Helm chart, Terraform scaffolding, Dockerfile, and CI/CD workflows -- all with correct cross-file coordination (metadata.id = Helm shortname = Terraform app_id). Use this skill when the user says "new project", "bootstrap", "scaffold", "create a new app", "set up a new service", or needs to generate the full infrastructure setup for a new application at Entur.

Generate Entur-standard CI/CD GitHub Actions workflows for a project. Detects language (Kotlin/Java, Go, Python) and generates all required workflow files: ci.yml, build.yml, cd.yml, pr.yml, codeql.yml, dependabot-pr.yml, terraform.yml, terraform-drift-detection.yml, and dependabot.yml. Use this skill when the user says "set up CI/CD", "create pipelines", "add GitHub Actions", "configure deployment", or needs CI/CD workflows for a new or existing Entur project. Always uses Entur reusable workflows -- never custom steps.

Entur platform conventions for code, infrastructure, deployment, and operations. Activate when editing or asking about: Kotlin/Java/Go/Python services, Spring Boot, Gradle, Helm charts, Dockerfiles, Terraform (Entur modules, IAM roles), Kafka, Pub/Sub, GCP, GKE, Cloud SQL, Memorystore, OAuth/OIDC, Permission Store, observability/logging/metrics, secrets and security scanning, GitHub Actions workflows, self-service `.entur/*.yaml` manifests, code review, or markdown style for an Entur application. Fetches the matching guide from the entur/ai repo on demand instead of bundling content.

Lag, forbedre eller strukturer innhold i SCR-format (Situasjon. Komplikasjon. Resolusjon). Bruk denne skillen alltid når brukeren nevner "SCR", "situasjon komplikasjon", "situation complication resolution", ber om å "drafte en SCR", "skrive en SCR", "lage en SCR", eller ber om hjelp til å presentere et problem eller en beslutning på en strukturert og overbevisende måte for ledelse eller interessenter. Skillen gjelder også når brukeren har råmateriale (punktlister, notater, møtereferater) og ønsker å omforme det til en klar, handlingsorientert fremstilling. SCR er særlig nyttig for arkitektur- og strategidiskusjoner, kost/nytte-vurderinger, veivalg og eskalering.

Internal architecture of json-schema/xsd-to-jsonschema.js — the GraalVM JavaScript converter that transforms NeTEx XSD schemas into annotated JSON Schema. Use when modifying the converter, debugging conversion output, adding new annotation passes, or understanding how XSD constructs map to JSON Schema. Trigger: /sub-graph or when editing xsd-to-jsonschema.js.

Autonomously refactor a change across the codebase, running tests in a loop until green, then rebuild and commit.

Generate OpenAPI 3.x schema components from XSD schemas with correct XML serialization annotations. Covers the xml: object (name, attribute, wrapped, namespace, prefix), XSD-to-OpenAPI mapping rules, and how to extend xsd-to-jsonschema.js to produce OpenAPI-compatible output. Use when converting XSD types to OpenAPI schemas, adding XML media type support to OpenAPI specs, or debugging XML serialization of OpenAPI-generated models.

Run AND keep healthy hathor's Playwright e2e suite — both mocked and against a LIVE local Sobek backend (E2E_BACKEND=true) — using the exact same sequential flow so the two modes stay identical, AND keeping the suite slim and true (no duplicate coverage, no unit-test-shaped specs). Use this whenever the user wants to run e2e against a real database / local backend, set up the manual-login + JWT-in-session (storageState) handoff, debug the "Loading data…" organisation-selection stall or a 401 from Sobek :37999 in tests, make mocked and live e2e behave the same way, audit that every spec follows the canonical login → select-org → navigate+count → create → edit-verify → edit sequence, or prune the suite (flag pure duplicate coverage and e2e tests that belong in vitest). Trigger eagerly on E2E_BACKEND, `e2e:local-backend`, "live backend e2e", "run e2e against the real DB", organisation-select stalls in tests, "why do my e2e tests hang / 401", "is this spec a duplicate", or "should this be a unit test" — even when

Generate a browsable top-down mermaid flowchart for every Playwright e2e spec by reading each spec's file-level JSDoc, then assemble them into one tmp index.html you can open in a browser. Use this whenever the user wants to visualize, diagram, map out, or "see" the e2e test suite / spec flows — e.g. "draw flowcharts for the e2e specs", "visualize the test workflows", "make a diagram of what each spec does", "render the spec JSDoc as charts", or any request to turn the e2e-tests/**/*.spec.ts keynote JSDoc into mermaid diagrams. Fans the work out across cheap (haiku) subagents — one per spec — so it stays fast and low-cost even on a large suite.

Upgrade Entur common Helm chart dependency from v1 to v2. Use this skill when the user wants to migrate their Helm values files to the v2 common chart, asks about upgrading to common chart v2, mentions "common chart upgrade", or has schema validation errors after bumping the common chart version. Also trigger when the user mentions deprecated fields like shortname, container.replicas, connectionConfig, memoryLimit, or postgres.instances with raw string values.

Validate, lint, and fix OpenAPI specs using the oav CLI. Use when the user works with OpenAPI specs, mentions API validation, linting, code generation errors, compile failures, .oavc config, or asks to check, fix, or set up validation for their API.