메뉴
Use when adding a new language/locale to the application — e.g. "add language", "add locale", "new language", "new translation", "internationalization". Touches Strapi admin config, Next.js i18n routing, and translation files.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when adding a new CMS entity that needs its own REST endpoint and DB table — e.g. "add content type", "new content type", "create strapi collection", "new single type", "add strapi model", "new entity". Not for page-builder sections; use `create-content-component` for those.
Use when adding a generic UI primitive, elementary block, or form field in `apps/ui` — e.g. "new ui component", "add component", "create react component", "new shadcn component", "add form field". Not for Strapi page-builder sections; use `create-content-component`.
Use as a checkpoint after building several page-builder components, to remove duplication — e.g. "consolidate patterns", "extract reusable", "dedupe components", "review components for shared patterns". Extracts JSX/Tailwind repeated across 2+ components into shared elementary components. React-only — never touches Strapi schemas.
Use to replicate a page-builder section from a reference — a text description, a screenshot, or an HTML/code snippet. Triggers: "copy component", "replicate component", "recreate this section", "build from screenshot", "make a component like this", "convert this HTML/JSX into a component", "port this section". Not for generic UI primitives (use `add-ui-component`) or API resources (use `add-content-type`).
Use when adding a new CMS-driven page section that lives in the page builder's dynamic zone — e.g. "add page component", "new page section", "page builder component", "create content component", "add section", "new strapi component". Not for top-level API resources (use `add-content-type`) or generic React components (use `add-ui-component`).
Use when checking whether a page-builder component already exists before building one — e.g. "find component", "does a component exist for", "is there a component that", "match this screenshot", "identify this section", "reuse existing component", "what renders this". Searches existing Strapi page-builder components by description or by a UI screenshot, then recommends reuse or `create-content-component`.
| name | add-locale |
| description | Use when adding a new language/locale to the application — e.g. "add language", "add locale", "new language", "new translation", "internationalization". Touches Strapi admin config, Next.js i18n routing, and translation files. |
Add a new language/locale across both apps. For the full file map and how i18n is wired, see apps/docs/docs/reference/internationalization.md.
Ask the user for both, then validate before proceeding:
de, fr, sk). Reject uppercase or invalid codes.German).Translation catalog — Copy apps/ui/locales/en.json to apps/ui/locales/{code}.json. Keep the keys identical; translate the values (or leave English and flag them for translation). Existing catalogs for reference: en.json, cs.json.
Routing — In apps/ui/src/lib/navigation.ts, add {code} to routing.locales, keeping the array alphabetical:
locales: ["cs", "en", "{code}"],
This is the only code change. The [locale] segment, generateStaticParams, the dynamic catalog import in apps/ui/src/lib/i18n.ts, and the Locale type (derived from routing.locales in apps/ui/src/types/global.d.ts) all pick up the new locale automatically.
Strapi + content — these are manual; tell the user:
See apps/docs/docs/reference/internationalization.md (Creating Localized Content) for details.