Run any Skill in Manus with one click

localize-routes

Stars23

Forks33

UpdatedMarch 13, 2026 at 08:33

Update language-aware routing and translation wiring in website-docs when the task changes locale behavior, top-level route prefixes, translation keys, page language availability, or Gatsby i18n configuration. Review gatsby-config.js matchPath rules, locale translation files, route generation assumptions, and any template or component code that depends on language-specific behavior.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

pingcap

pingcap/website-docs

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

File Explorer

2 files

SKILL.md

readonly

name	localize-routes
description	Update language-aware routing and translation wiring in website-docs when the task changes locale behavior, top-level route prefixes, translation keys, page language availability, or Gatsby i18n configuration. Review gatsby-config.js matchPath rules, locale translation files, route generation assumptions, and any template or component code that depends on language-specific behavior.

Localize Routes

Overview

Use this skill for changes that affect locale prefixes, translation dictionaries, or Gatsby i18n routing behavior. This repo uses gatsby-plugin-react-i18next with manual matchPath rules and language-aware page structures, so routing changes usually touch more than one file.

Workflow

1) Identify the scope of the i18n change

Typical triggers:

New translation keys in UI
New or renamed top-level route prefixes
Locale-specific availability differences
Language-dependent banner, navigation, or SEO behavior

2) Review the Gatsby i18n entrypoint

Inspect gatsby-config.js, especially:

languages
defaultLanguage
redirect
pages[].matchPath
getLanguageFromPath

In this repo, route families under docs prefixes are explicitly listed in matchPath. New top-level prefixes often require updates there.

3) Update translation files when UI text changes

Edit:

locale/en/translation.json
locale/zh/translation.json
locale/ja/translation.json

Rules:

Keep keys consistent across locales
Only add the languages actually supported by the feature
Reuse existing namespaces and key naming conventions when possible

4) Review routing helpers and consumers

Depending on the task, also inspect:

gatsby/create-pages/*
src/templates/*
src/components/Layout/Header/LangSwitch.tsx
components using useI18next, Trans, or locale-aware branching

Be especially careful when changing:

omission of /en/
route prefixes like developer, best-practices, api, ai, releases
locale availability shown in UI via availIn.locale

5) Validate

At minimum:

Confirm matchPath covers the affected route family
Confirm new translation keys exist in all intended locale files
Confirm any locale-conditional UI logic still behaves correctly
Run yarn build when feasible

Output Checklist

Report:

Which locale and routing files changed
Whether gatsby-config.js matchPath was reviewed or changed
Which translation keys were added or updated
Any language-specific limitations
Whether yarn build was run

More from this repository

same repository

dev-browser

pingcap/website-docs

Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.

2026-03-1323

create-pages

pingcap/website-docs

Create or update a page-generation workflow in website-docs when the task adds a new Gatsby page type, template-backed route, or build-time page creation rule. Implement the page creator under gatsby/create-pages/, connect the correct template under src/templates/, pass pageContext consistently, and review routing, i18n, and build-type behavior.

2026-03-1323

create-plugin

pingcap/website-docs

Create or update repository-local Gatsby MDX plugins in website-docs when the task requires custom Markdown transformation, AST rewriting, shortcode conversion, or remark/rehype-style behavior during build. Implement the plugin under gatsby/plugin/, register it from gatsby-config.js, connect it to MDX components when JSX output is needed, and verify the affected Markdown rendering path.

2026-03-1323

extend-mdx

pingcap/website-docs

Extend MDX rendering in website-docs when a request needs either a new custom MDX component that authors can invoke with JSX-like tags, or a build-time Markdown-to-MDX transform that compiles plain Markdown syntax into custom JSX/AST behavior. Implement runtime components under src/components/MDXComponents/, implement build-time transforms under gatsby/plugin/, register exports and plugins in the right places, and validate the end-to-end MDX rendering path.

2026-03-1323

integrate-search

pingcap/website-docs

Update onsite search behavior in website-docs when the task changes the search page, search box flows, Algolia client wiring, result categorization, external search fallbacks, or search-related routing. Edit the relevant Gatsby page creator, search template or components, and shared search utilities while keeping locale, category, and tracking behavior aligned.

2026-03-1323

manage-toc

pingcap/website-docs

Modify TOC extraction, navigation generation, or TOC-based filtering behavior in website-docs when the task changes how document navigation trees, right-side headings, or TOC membership are computed. Update the Gatsby TOC pipeline under gatsby/, keep runtime filtering logic in src/shared/ aligned, and add or adjust Jest coverage for the changed TOC behavior.

2026-03-1323

name	localize-routes
description	Update language-aware routing and translation wiring in website-docs when the task changes locale behavior, top-level route prefixes, translation keys, page language availability, or Gatsby i18n configuration. Review gatsby-config.js matchPath rules, locale translation files, route generation assumptions, and any template or component code that depends on language-specific behavior.

Localize Routes

Overview

Workflow

1) Identify the scope of the i18n change

Typical triggers:

New translation keys in UI
New or renamed top-level route prefixes
Locale-specific availability differences
Language-dependent banner, navigation, or SEO behavior

2) Review the Gatsby i18n entrypoint

Inspect gatsby-config.js, especially:

languages
defaultLanguage
redirect
pages[].matchPath
getLanguageFromPath

In this repo, route families under docs prefixes are explicitly listed in matchPath. New top-level prefixes often require updates there.

3) Update translation files when UI text changes

Edit:

locale/en/translation.json
locale/zh/translation.json
locale/ja/translation.json

Rules:

Keep keys consistent across locales
Only add the languages actually supported by the feature
Reuse existing namespaces and key naming conventions when possible

4) Review routing helpers and consumers

Depending on the task, also inspect:

gatsby/create-pages/*
src/templates/*
src/components/Layout/Header/LangSwitch.tsx
components using useI18next, Trans, or locale-aware branching

Be especially careful when changing:

omission of /en/
route prefixes like developer, best-practices, api, ai, releases
locale availability shown in UI via availIn.locale

5) Validate

At minimum:

Confirm matchPath covers the affected route family
Confirm new translation keys exist in all intended locale files
Confirm any locale-conditional UI logic still behaves correctly
Run yarn build when feasible

Output Checklist

Report:

Which locale and routing files changed
Whether gatsby-config.js matchPath was reviewed or changed
Which translation keys were added or updated
Any language-specific limitations
Whether yarn build was run