FixMyBerlin

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, Cursor MCP (Postgres, agent-browser), and when to pick sibling skills. Use when scaffolding a new app, evaluating libraries, setting up Bun install/global store or Knip, changing supported browsers or compat lint, setting up Cursor MCP, or making stack/architecture decisions on existing apps.

Premium orchestrator (Fable 5, Sonnet 5, or GPT-5.6 Sol) with Composer 2.5 workers. Two separate setups: Cursor IDE (subagents in .cursor/agents) or Claude Code (cursor-agent CLI + .claude/skills). Use when configuring orchestration; pick the guide for your host.

FMC finish-work workflow: run bun run check, fix failures, commit with a user-facing English message by default, and only show a draft when the user clearly did not want a commit. Use for finish work, run checks, wrap up, land changes, or create commits.

E2E testing and browser automation for TanStack Start apps (FMC/TILDA). Use @playwright/test for committed suites/CI; agent-browser MCP (skill tech-stack) for agent exploration; this skill for smoke tests, stubbed auth, map hooks, and quick /tmp scripts. Not for Next.js.

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, window.__mainMap debug exposure, 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, map URL sync, or agent/test map inspection in TanStack Start / Vite apps. Reference implementation: tilda-geo/app.

Review and merge open Dependabot PRs in the current workspace repo: changelog triage, risk classification, CI verification, and rebase merge. Use for "/review dependabot" or similar — always scoped to the repo you have open. Weekly Bun/GitHub Actions/Docker bumps, grouped patches, security updates, semver-major upgrades.

Direct-to-S3 uploads in TanStack Start with @better-upload/server and @better-upload/client (presigned PUT, API route POST handlers, useUploadFiles/useUploadFile, S3 object helpers). Optional react-dropzone add-on only for multi-file drag-and-drop UX. Use for upload API routes, presigned S3, upload progress, post-upload DB persistence, or the dropzone component stack.

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, Cursor MCP (Postgres, agent-browser), and when to pick sibling skills. Use when scaffolding a new app, evaluating libraries, changing supported browsers or compat lint, setting up Cursor MCP, or making stack/architecture decisions on existing apps.

FMC finish-work workflow: run bun run check, fix failures, commit with a user-facing English message by default, and only show a draft when the user clearly did not want a commit. Use for finish work, run checks, wrap up, land changes, or create commits.

Trassenscout-specific Better Auth wiring: endpointAuth boundary API, route protection via auth.functions.ts, and oxlint enforcement. Pair with shared skill tanstack-start-auth for Better Auth library config.

E2E testing and browser automation for TanStack Start apps (FMC/TILDA). Use @playwright/test for committed suites/CI; agent-browser MCP (skill tech-stack) for agent exploration; this skill for smoke tests, stubbed auth, map hooks, and quick /tmp scripts. Not for Next.js.

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, window.__mainMap debug exposure, 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, map URL sync, or agent/test map inspection in TanStack Start / Vite apps. Reference implementation: tilda-geo/app.

TanStack Start and Router conventions for FixMyBerlin/FMC: app folder layout, thin routes, client/server file suffixes, loaders vs React Query, selective SSR, experimental server components (RSC), router search serialization (clean share URLs), and UI vs API route param/search validation. Use when scaffolding or refactoring app/src structure, working on TanStack Start routes, server functions, loaders, router.tsx parseSearch/stringifySearch, renderServerComponent, createCompositeComponent, validateSearch, or API routes under routes/api/.

Weekly end-user release notes from Git commits — German prose in docs/user-changelog.md, not a technical changelog. Reads commit subjects and bodies; diffs only when needed. SHA boundaries in section headings avoid duplicate work. Use for user changelog, weekly user summary, end-user release notes, or Nutzer-Zusammenfassung.

Orchestrate greenfield FixMyBerlin/FMC repo bootstrap: plan which fixmyskills to install, git init, AGPL license, three finish-work commits. Use when scaffolding a new project or onboarding a new repo. Delegates to finish-work, tech-stack, and agent-orchestration — do not duplicate their steps.

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, Cursor MCP (Postgres, agent-browser), and when to pick sibling skills. Use when scaffolding a new app, evaluating libraries, setting up Bun install/global store or Knip, changing supported browsers or compat lint, setting up Cursor MCP, or making stack/architecture decisions on existing apps.

Orchestrator (Grok 4.5, Fable 5, Sonnet 5, or GPT-5.6 Sol) with Composer 2.5 workers. Two separate setups: Cursor IDE (subagents in .cursor/agents) or Claude Code (cursor-agent CLI + .claude/skills). Use when configuring orchestration; pick the guide for your host.

DEPRECATED — FMC Next.js → TanStack Start migrations are complete. Use tanstack-start-conventions and react-dev instead. Archived reference only; not installable via skills CLI.

nuqs (type-safe URL query state) for Next.js and legacy/shared components. Prefer TanStack Router validateSearch on TanStack Start/Router apps. Use when writing nuqs hooks, parsers, NuqsAdapter setup, or Next.js URL state — not for greenfield TanStack route search params.

E2E testing and browser automation for TanStack Start apps (FMC/TILDA). Use @playwright/test for committed suites/CI; agent-browser MCP (skill tech-stack) for agent exploration; this skill for smoke tests, stubbed auth, map hooks, and quick /tmp scripts. Not for Next.js.

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).

TanStack Start and Router conventions for FixMyBerlin/FMC: app folder layout, thin routes, client/server file suffixes, loaders vs React Query, selective SSR, experimental server components (RSC), router search serialization (clean share URLs), and UI vs API route param/search validation. Use when scaffolding or refactoring app/src structure, working on TanStack Start routes, server functions, loaders, router.tsx parseSearch/stringifySearch, renderServerComponent, createCompositeComponent, validateSearch, or API routes under routes/api/.

Documents how to validate changes locally with this repository's Bun-based smoke and runtime tests. Use when the user asks to test changes locally, verify behavior before commit, debug failing local checks, or choose the right test command for the scope of a change.

Guides work in this Bun-based workspace with strict Bun runtime conventions for scripts, shell execution, env loading, and Bun test usage.