next-intl-server-runtime
Next Intl Server Runtime
Use this skill when the task is about request-scoped config, server-side API selection, or rendering correctness across server and client boundaries.
Scope
i18n/request.ts,getRequestConfig, andrequestLocale- component environment rules for hooks vs awaitable APIs
NextIntlClientProviderinheritance, opt-out, and client wrapperssetRequestLocaleand static rendering- metadata, Server Actions, Route Handlers, sitemap, manifest, and OG images
- error files and testing translated components
Routing cues
getRequestConfig,requestLocale,NextIntlClientProvider,setRequestLocale, metadata, Server Actions, Route Handlers, sitemap, manifest, OG images, error files, tests -> use this skill- locale routing, domains, pathnames, locale switchers -> use
next-intl-routing-and-navigation - ICU authoring,
t.rich,useFormatter, message validation -> usenext-intl-messages-and-formatting - plugin flags, augmentation, Crowdin,
useExtracted-> usenext-intl-workflows-and-tooling
More from dobroslavradosavljevic/skills
base-ui-typescript-surface
Use for Base UI namespace contracts, change event types, generic render types, and wrapper typing patterns.
4base-ui-basic-primitives
Use for simple primitives with low integration complexity (Avatar, Button, Meter, Progress, Scroll Area, Separator).
4base-ui-root-providers
Use for CSP Provider, Direction Provider, and useDirection when wiring Base UI at the app root or across portals.
4base-ui-menus-navigation-and-toast
Use for Menu, Context Menu, Menubar, Navigation Menu, Toolbar, Toast, and shared command-surface patterns such as detached triggers and menu payloads.
4base-ui-forms-and-validation
Use for Base UI Field/Form primitives, validation flows, form controls, and advanced Number Field, Slider, and RadioGroup behavior.
4base-ui-disclosure-and-tabs
Use for stateful visibility components (Accordion, Collapsible) and tab navigation semantics.
4