Admin Template Project Initializer
southliu/south-admin-react
Removes the south-admin-react template's demo pages, components and menu entries, after a dry-run preview and your confirmation, and cleans up the matching imports.
Migrate i18next/react-i18next projects to Lingui. An agent skill from B0und/WikiSpeedrun.
$ npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install B0und/WikiSpeedrun migrate-i18next-to-lingui --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/B0und/WikiSpeedrun.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/migrate-i18next-to-lingui .claude/skills/migrate-i18next-to-lingui && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "migrate-i18next-to-lingui" agent skill from https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-lingui into .claude/skills/migrate-i18next-to-lingui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-i18next-to-lingui", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-linguiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install B0und/WikiSpeedrun migrate-i18next-to-lingui --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/B0und/WikiSpeedrun.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/migrate-i18next-to-lingui .agents/skills/migrate-i18next-to-lingui && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migrate-i18next-to-lingui" agent skill from https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-lingui into .agents/skills/migrate-i18next-to-lingui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-i18next-to-lingui", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install B0und/WikiSpeedrun migrate-i18next-to-lingui --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/B0und/WikiSpeedrun.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/migrate-i18next-to-lingui .cursor/skills/migrate-i18next-to-lingui && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "migrate-i18next-to-lingui" agent skill from https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-lingui into .cursor/skills/migrate-i18next-to-lingui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-i18next-to-lingui", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/B0und/WikiSpeedrun.git --path .agents/skills/migrate-i18next-to-lingui--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install B0und/WikiSpeedrun migrate-i18next-to-lingui --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/B0und/WikiSpeedrun.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/migrate-i18next-to-lingui .gemini/skills/migrate-i18next-to-lingui && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "migrate-i18next-to-lingui" agent skill from https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-lingui into .gemini/skills/migrate-i18next-to-lingui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-i18next-to-lingui", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install B0und/WikiSpeedrun migrate-i18next-to-linguiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/B0und/WikiSpeedrun.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/migrate-i18next-to-lingui .github/skills/migrate-i18next-to-lingui && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "migrate-i18next-to-lingui" agent skill from https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-lingui into .github/skills/migrate-i18next-to-lingui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-i18next-to-lingui", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install B0und/WikiSpeedrun migrate-i18next-to-lingui --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/B0und/WikiSpeedrun.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/migrate-i18next-to-lingui .opencode/skills/migrate-i18next-to-lingui && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "migrate-i18next-to-lingui" agent skill from https://github.com/B0und/WikiSpeedrun/tree/main/.agents/skills/migrate-i18next-to-lingui into .opencode/skills/migrate-i18next-to-lingui/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migrate-i18next-to-lingui", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
migrate-i18next-to-linguiMigrate i18next/react-i18next projects to Lingui. An agent skill from B0und/WikiSpeedrun.
Migrate I18next To Lingui is an agent skill from B0und/WikiSpeedrun. Migrate i18next/react-i18next projects to Lingui. Use when the user wants to replace i18next, react-i18next, useTranslation, i18n.t(), Trans i18nKey, or i18next JSON catalogs with Lingui equivalents. Covers package installation, config setup, code transformation patterns, plural migration, namespace handling, and catalog conversion.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/catalog-conversion.md` and `references/migration-patterns.md`).
It sits in Frontend & Design, covering Internationalization. It works with React, Vite and TypeScript. The repository describes itself as: Wikipedia Speedrun Game. The licence is MIT.
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a03d655. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
npmnpxFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
lingui.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Migrate I18next To Lingui loads about 3.1k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 90 tokens; SKILL.md has 645 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from B0und/WikiSpeedrun at commit a03d655, republished under its MIT licence (© B0und). 645 words, ~3,056 tokens.
.claude/skills/migrate-i18next-to-lingui/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- [ ] Step 1: Install Lingui packages
- [ ] Step 2: Create lingui.config.js
- [ ] Step 3: Set up build tooling (Babel/SWC/Vite)
- [ ] Step 4: Replace i18n initialization
- [ ] Step 5: Migrate React components (useTranslation → useLingui, Trans → Trans)
- [ ] Step 6: Migrate JS/TS strings (t() → t``)
- [ ] Step 7: Migrate plurals
- [ ] Step 8: Migrate namespaces
- [ ] Step 9: Convert existing translation catalogs
- [ ] Step 10: Run lingui extract && lingui compile
- [ ] Step 11: Remove i18next packagesNode version gate: Lingui 6 is ESM-only and requires Node.js ≥ 22.19 (or ≥ 24). On older Node, pin all
@lingui/*packages to^5.
# Core (always required)
npm install @lingui/core @lingui/react
# CLI (dev)
npm install --save-dev @lingui/cli
# Macro support - pick one based on build tool:
# Babel
npm install --save-dev @lingui/babel-plugin-lingui-macro
# SWC
npm install --save-dev @lingui/swc-plugin
# Vite (also install the Babel macro plugin above — see Step 3)
npm install --save-dev @lingui/vite-pluginlingui.config.jsimport { defineConfig } from "@lingui/cli";
export default defineConfig({
sourceLocale: "en",
locales: ["en", "de", "fr"], // match your existing locales
catalogs: [
{
path: "<rootDir>/src/locales/{locale}/messages",
include: ["src"],
},
],
});Vite (vite.config.ts):
import { lingui } from "@lingui/vite-plugin";
import react from "@vitejs/plugin-react";
export default {
plugins: [
react({ babel: { plugins: ["@lingui/babel-plugin-lingui-macro"] } }),
lingui(),
],
};lingui() alone does not transform macros — the Babel macro plugin inside react() does that (requires @vitejs/plugin-react@^5; v6 removed the babel option — use the SWC variant instead).
The lingui() plugin also compiles .po catalogs on the fly, so on Vite the app can import catalogs directly and skip the lingui compile step entirely:
// Dynamic import; the .po extension is mandatory
const { messages } = await import(`./locales/${locale}/messages.po`);For TypeScript, declare the module so .po imports type-check:
// src/vite-env.d.ts
declare module "*.po" {
import type { Messages } from "@lingui/core";
export const messages: Messages;
}Babel (.babelrc or babel.config.js):
{ "plugins": ["macros"] }Next.js with SWC (next.config.js):
module.exports = {
experimental: {
swcPlugins: [["@lingui/swc-plugin", {}]],
},
};Build-tooling caveats: @lingui/swc-plugin must be version-matched to your SWC runtime, plugin entries must be [name, options] tuples (a bare string silently disables macros), and @vitejs/plugin-react@6 removed Babel support entirely — see the swc-plugin-compatibility skill for all three.
Before (i18next):
import i18next from "i18next";
import { initReactI18next } from "react-i18next";
i18next.use(initReactI18next).init({
lng: "en",
resources: { en: { translation: { key: "Hello world" } } },
});After (Lingui):
import { i18n } from "@lingui/core";
import { I18nProvider } from "@lingui/react";
import { messages } from "./locales/en/messages";
i18n.load("en", messages);
i18n.activate("en");
function App() {
return <I18nProvider i18n={i18n}>{/* app */}</I18nProvider>;
}Dynamic locale switching:
async function changeLocale(locale) {
const { messages } = await import(`./locales/${locale}/messages`);
i18n.load(locale, messages);
i18n.activate(locale);
}useTranslation → useLinguiBefore:
import { useTranslation } from "react-i18next";
function MyComponent() {
const { t } = useTranslation();
return <p>{t("greeting")}</p>;
}After:
import { useLingui } from "@lingui/react/macro";
function MyComponent() {
const { t } = useLingui();
return <p>{t`Hello World`}</p>;
}Trans componentBefore:
import { Trans } from "react-i18next";
<Trans i18nKey="welcome">Hello World!</Trans>After:
import { Trans } from "@lingui/react/macro";
<Trans>Hello World!</Trans>For explicit IDs (when preserving i18next keys):
<Trans id="welcome">Hello World!</Trans>Trans with interpolationBefore:
<Trans i18nKey="greeting" values={{ name }}>Hello {{ name }}!</Trans>After:
<Trans>Hello {name}!</Trans>| i18next | Lingui |
|---|---|
t('key') | t\Message text`` |
t('key', { name }) | t\Hello ${name}`` |
t('key', { defaultValue: 'Hi' }) | t\Hi`` |
Before:
import i18next from "i18next";
const msg = i18next.t("greeting", { name: "Tom" });After:
import { useLingui } from "@lingui/react/macro";
function MyComponent() {
const { t } = useLingui();
const msg = t`Hello ${name}`;
}In vanilla JS (outside components):
import { t } from "@lingui/core/macro";
const msg = t`Hello ${name}`;If you want to keep the i18next message IDs:
import { t } from "@lingui/core/macro";
// i18next: t('navigation.home')
const msg = t({ id: "navigation.home", message: "Home" });Before (i18next):
const LABELS = {
active: "Active",
inactive: "Inactive",
};
// translated at render timeAfter (Lingui):
import { msg } from "@lingui/core/macro";
import { useLingui } from "@lingui/react";
const LABELS = {
active: msg`Active`,
inactive: msg`Inactive`,
};
function StatusDisplay({ status }) {
const { _ } = useLingui();
return <div>{_(LABELS[status])}</div>;
}i18next uses separate keys per plural form. Lingui uses ICU MessageFormat in a single message.
Before (i18next):
{
"item_one": "{{count}} item",
"item_other": "{{count}} items"
}t("item", { count });After (Lingui) - JSX:
import { Plural } from "@lingui/react/macro";
<Plural value={count} one="# item" other="# items" />After (Lingui) - JS strings:
import { plural } from "@lingui/core/macro";
const msg = plural(count, {
one: "# item",
other: "# items",
});Exact matches (i18next _0):
<Plural
value={count}
_0="No items"
one="# item"
other="# items"
/>i18next namespaces (useTranslation('common')) map to Lingui catalog paths. Two approaches:
Option A - Single catalog (simplest):
Remove namespaces and use one unified catalog. Update lingui.config.js to include all source directories.
Option B - Multiple catalogs (preserves namespace separation):
// lingui.config.js
catalogs: [
{
path: "<rootDir>/src/locales/{locale}/common",
include: ["src/components/common"],
},
{
path: "<rootDir>/src/locales/{locale}/auth",
include: ["src/components/auth"],
},
]With multiple catalogs, load them all at startup:
import { messages as commonMessages } from "./locales/en/common";
import { messages as authMessages } from "./locales/en/auth";
i18n.load("en", { ...commonMessages, ...authMessages });
i18n.activate("en");See catalog-conversion.md for and patterns.
Key concept: i18next uses JSON with dotted keys; Lingui uses .po files with the message as the ID (or an explicit ID you provide).
Run the full verification loop in this order — each stage catches what the previous one can't:
npx lingui extract --clean # extracts all messages → .po files, drops obsolete entries
npx lingui compile # compiles .po → runtime message catalogs
npx tsc --noEmit # type errors from changed imports/APIs
npm run build # macro transform actually runs in the real buildOn Vite with @lingui/vite-plugin importing .po catalogs directly (Step 3), skip lingui compile — the plugin compiles at dev/build time and there are no compiled catalog files to manage.
Add to package.json:
{
"scripts": {
"i18n:extract": "lingui extract",
"i18n:compile": "lingui compile"
}
}For TypeScript:
npx lingui compile --typescriptA green build only proves the migrated strings work — not that all strings were migrated. Two checks:
1. No i18next remnants. All of these should return nothing:
grep -rn "from ['\"]i18next\|from ['\"]react-i18next" src/
grep -rn "useTranslation\|i18nKey\|i18next.t(" src/2. No unwrapped user-facing strings. Run eslint-plugin-lingui's no-unlocalized-strings rule over the tree — it catches hardcoded strings that were never in i18next to begin with, plus any defaultValue text left behind as plain strings:
// eslint.config.js
import pluginLingui from "eslint-plugin-lingui";
export default [
{
plugins: { lingui: pluginLingui },
rules: {
"lingui/no-unlocalized-strings": ["warn", {
ignore: ["^[A-Z0-9_-]+$"], // enums, constants
ignoreNames: ["className", "src", "data-testid"],
ignoreFunctions: ["console.*", "cn", "cva"],
}],
},
},
];The scan is deliberately over-inclusive — review each hit and either wrap it or confirm it's a non-UI string (class names, keys, URLs). Keep the plugin installed afterwards as a permanent guardrail. Report any strings you deliberately leave unwrapped rather than silently skipping them.
For the full audit loop — tuned scanner config, bounded fix rounds, residual reporting — use the find-unwrapped-strings skill. The check above is its migration-scoped subset.
npm uninstall i18next react-i18nextBefore (i18next):
t("intlDateTime", { val: new Date() });After (Lingui):
import { useLingui } from "@lingui/react/macro";
function Component() {
const { i18n } = useLingui();
return <span>{new Intl.DateTimeFormat(i18n.locale).format(date)}</span>;
}Before (i18next):
t("right", { context: "direction" });After (Lingui):
<Trans context="direction">right</Trans>
// or
t({ message: "right", context: "direction" });Before (i18next):
{ "pronoun_male": "He", "pronoun_female": "She", "pronoun_other": "They" }After (Lingui):
import { select } from "@lingui/core/macro";
const pronoun = select(gender, {
male: "He",
female: "She",
other: "They",
});t\...`` at module level. Use msg\...`instead and translate with_(descriptor)` at render time.i18n.load(locale, messages) and i18n.activate(locale).<I18nProvider i18n={i18n}> before any component uses useLingui or Trans.lingui compile before building for production; the app imports compiled .js catalogs, not .po files.id props.© B0und, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in .agents/skills/migrate-i18next-to-lingui of B0und/WikiSpeedrun.
Open the folder on GitHubat commit a03d655
Migrate I18next To Lingui next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Migrate I18next To Lingui this skillB0und/WikiSpeedrun | 133 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Admin Template Project Initializersouthliu/south-admin-react | 580 | — | ~519 | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 40 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Lobe Designlobehub/lobe-ui | 2.2k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Frontend Build Timing Auditopenops-cloud/openops | 1.1k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Design To CodeMigoXLab/coderio | 114 | 2 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 |
southliu/south-admin-react
Removes the south-admin-react template's demo pages, components and menu entries, after a dry-run preview and your confirmation, and cleans up the matching imports.
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
lobehub/lobe-ui
Build UI with the LobeHub design system — @lobehub/ui/base-ui, the controlled form at @lobehub/ui/base-ui/form, and the chat, mobile, dashboard, awesome, brand, mdx, and i18n namespaces, plus…
openops-cloud/openops
Detects and diagnoses chunk-evaluation timing bugs in the Vite/rolldown production build of react-ui (works-in-dev / broken-in-build i18n regressions, missing UI labels, module-scope t()…
MigoXLab/coderio
Pixel-perfect Figma to React conversion using coderio. An agent skill from MigoXLab/coderio.
southliu/south-admin-react
Generates a full CRUD page - page component, data model and API client - from the south-admin-react project's own VS Code snippet templates.
B0und/WikiSpeedrun
Implement internationalization with Lingui in React and JavaScript applications.
B0und/WikiSpeedrun
Audit a Lingui project for hardcoded user-facing strings that were never wrapped in macros.
B0und/WikiSpeedrun
Set up Lingui in a React framework. An agent skill from B0und/WikiSpeedrun.
B0und/WikiSpeedrun
Add translator comments to Lingui messages so translations are accurate.
B0und/WikiSpeedrun
Diagnose and fix Lingui SWC plugin compatibility errors with Next.js, Vite, Rspack, or other SWC runtimes.
Works with
Categories
Migrate i18next/react-i18next projects to Lingui. An agent skill from B0und/WikiSpeedrun. Migrate I18next To Lingui is an agent skill from B0und/WikiSpeedrun. Migrate i18next/react-i18next projects to Lingui.
Migrate I18next To Lingui fits situations like: the user wants to replace i18next; I18next JSON catalogs with Lingui equivalents.
Run `npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a claude-code`. Or copy the skill folder (.agents/skills/migrate-i18next-to-lingui in B0und/WikiSpeedrun) into .claude/skills/migrate-i18next-to-lingui in your project. Claude Code loads it when a task matches its description.
Run `npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a codex`. Or copy the skill folder (.agents/skills/migrate-i18next-to-lingui in B0und/WikiSpeedrun) into .agents/skills/migrate-i18next-to-lingui in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add B0und/WikiSpeedrun --skill migrate-i18next-to-lingui -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migrate-i18next-to-lingui, .gemini/skills/migrate-i18next-to-lingui, .github/skills/migrate-i18next-to-lingui and .opencode/skills/migrate-i18next-to-lingui in your project.
Going by SKILL.md and its folder, Migrate I18next To Lingui needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js.
SKILL.md names 1 domain. As links in the text: lingui.dev. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Migrate I18next To Lingui is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Migrate I18next To Lingui: Admin Template Project Initializer (southliu/south-admin-react, 580 stars), Web Artifacts Builder (anthropics/skills, 180k stars), Lobe Design (lobehub/lobe-ui, 2.2k stars) and Frontend Build Timing Audit (openops-cloud/openops, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
B0und (a GitHub user) maintains it in B0und/WikiSpeedrun, which has 133 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 19, 2026.
Source: B0und/WikiSpeedrun on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.