菜单
Use when adding or changing translations in messages/ja.json or messages/en.json, using getTranslations/useTranslations, or updating next-intl configuration under src/i18n/. Covers message key hierarchy, Server/Client Component APIs, dynamic and rich-text patterns, and JSON duplicate-key pitfalls.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when creating pages under src/app/(site)/(authorized)/admin/. Covers list/detail/edit/create page patterns with DataTable/DataView/DataForm, repositories under src/repositories/, request schemas under src/requests/admin/, and AdminPageHeader breadcrumbs.
Use when modifying Better Auth + Prisma authentication: src/libraries/auth.ts, src/libraries/auth-client.ts, src/proxy.ts, src/services/auth_service.ts, auth-related actions.ts, or prisma/schema.prisma auth models (User/Session/Account/Verification). Covers session helpers, URL/secret env resolution, DB TLS, and PUBLIC_PATHS.
Use when creating or modifying files under src/repositories/, src/models/, or src/requests/. Covers BaseRepository inheritance (Prisma/API/Local/Airtable/Dify), Zod schema placement, and separation between repository and schema files.
Use when changing this template's mail delivery backend, reviewing email env setup, switching between `ses` and `smtp`, or adding a new provider such as Resend, SendGrid, Postmark, or Mailgun. Covers EMAIL_PROVIDER routing, EMAIL_FROM priority, dynamic import for Node-only SDKs, and test coverage for both email.test.ts and Better Auth callback smoke.
Use when adding or modifying pages under src/app, or components under src/components (atoms/molecules/organisms) in this Next.js App Router project. Covers Server/Client Component boundary, Atomic Design placement, Server Actions in actions.ts, URL-based state management, sidebar active-state, and shadcn-only atoms rule.
Use when changing this template's object storage backend, reviewing storage env setup, switching between `s3`, `s3-compatible`, and `gcs`, or adding a new provider such as R2, MinIO, Spaces, Azure Blob, or GCS. Covers STORAGE_PROVIDER routing, S3Provider reuse for compatible services, forcePathStyle handling, SYSTEM_AWS_* env, and separation from image-display CSP/EXTRA_REMOTE_IMAGE_URLS.
| name | i18n-messages |
| description | Use when adding or changing translations in messages/ja.json or messages/en.json, using getTranslations/useTranslations, or updating next-intl configuration under src/i18n/. Covers message key hierarchy, Server/Client Component APIs, dynamic and rich-text patterns, and JSON duplicate-key pitfalls. |
UI に表示する全テキストは next-intl 経由。messages/ja.json と messages/en.json を同時更新する。正本は docs/guides/i18n.md。
messages/ja.json / messages/en.json を編集するsrc/i18n/routing.ts / src/i18n/request.ts を変更するWhen NOT to use: 新規ページ・コンポーネント作成自体は creating-pages-components（その中で翻訳も当然使う）。
messages/ja.json と messages/en.json を必ず同時更新。片方だけの追加は禁止getTranslations("Namespace")、Client Component → useTranslations("Namespace")。逆は使えないAsia/Tokyo 固定（src/i18n/request.ts 参照）機能別・コンポーネント別にネスト。共通文言は Common / Crud にまとめる。
{
"Auth": { "signin": "ログイン", "email": "メールアドレス" },
"Menu": { "Admin": { "users": "ユーザー" } },
"Common": { "buttons": { "save": "保存", "cancel": "キャンセル" } }
}
// Server
const t = await getTranslations("Menu.Admin");
t("users");
// Client
"use client";
const tAuth = useTranslations("Auth");
tAuth("signin");
// 動的
t("welcome", { name: "山田太郎" });
// Rich text
t.rich("description", { link: (chunks) => <Link href="/x">{chunks}</Link> });
messages/ja.json / messages/en.json — 翻訳本体src/i18n/routing.ts — ロケール・パス名設定src/i18n/request.ts — getRequestConfig、タイムゾーンsrc/app/providers.tsx — NextIntlClientProvider ラップsrc/app/layout.tsx — getLocale() / getMessages() 取得docs/guides/i18n.mdAGENTS.md §国際化（i18n）messages/ja.json と messages/en.json の 両方に同じキーで追加getTranslations / useTranslations）を使用data-testid ベース）