www.osm-verkehrswende.org

Run FMC pre-commit verification (bun run check, bun run format), fix failures, and draft commit messages. Use when finishing a task, wrapping up changes, preparing to commit, running checks/tests/lint/typecheck/e2e, or when the user asks to "finish work", "run checks", or "create a commit message".

React 19 + TypeScript for FMC TanStack Start apps: typed components, events, generics, ref-as-prop, Compiler-first memoization, and useEffect discipline (naming, when not to use Effect, alternatives). Use when typing React components/hooks/events, or writing/reviewing useEffect, useEffectEvent, derived state, data-fetch effects, or eslint-plugin-react-hooks effect rules. Not for routing/server boundaries (see tanstack-start-* skills).

react-map-gl/maplibre patterns for FMC geo apps: declarative Source/Layer (never addSource/addLayer), MapProvider + useMap(), interactiveLayerIds, flat Source/Layer, map-loaded guard, Map event handlers (not useEffect), URL map state, initialViewState, cursor, feature state, missing images. Use when building or reviewing Map components, layers, click/hover handlers, setFeatureState, or map URL sync in TanStack Start / Vite apps. Reference implementation: tilda-geo/app.

Review and merge Dependabot PRs for FMC repos (tilda-geo, trassenscout, etc.): changelog triage, risk classification, CI verification, and rebase merge. Use when triaging dependency update PRs, weekly Bun/GitHub Actions/Docker bumps, grouped patch PRs, security updates, or semver-major upgrades.

Default FMC tech stack for geo-heavy React SPAs: Bun/Vite, React 19, TanStack, maps, styling, TypeScript editor/CLI alignment, tsconfig templates, browserslist client targets, and when to pick sibling skills. Use when scaffolding a new app, evaluating libraries, changing supported browsers or compat lint, or making stack/architecture decisions on existing apps.

FMC conventions for Zustand v5 in React: file naming, custom-hook-only exports, atomic selectors, actions namespace, small focused stores. Use when adding or reviewing client global state, or debugging unnecessary re-renders and SSR/persist hydration issues. Not for server/async data (TanStack Query) or URL state (nuqs). For API details, middleware, slices, and migration, use the official llms.txt index below.