菜单
Add localization keys and use them in elements or controllers. Use when adding user-facing text that should be translatable — labels, descriptions, error messages, button text, status text, or any string shown in the backoffice UI.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/umbraco/Umbraco-CMS --skill general-add-localization命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Automated PR code review for Umbraco CMS. Analyzes changed files for intent, impact on consumers, breaking changes, architecture compliance, and code quality. Non-interactive — outputs a full structured review. Use this skill whenever the user asks to review a branch, review a PR, check their changes for issues, analyze a diff, or validate breaking change patterns — even if they don't say "review" explicitly. Does NOT apply to writing new code, fixing bugs, refactoring, explaining architecture, writing tests, or reviewing documentation content.
Regenerate the Management API OpenApi.json for Umbraco CMS from a running backend, and optionally regenerate the backoffice hey-api client so its generated types match. Proactively offer to run this at the end of any work that adds, removes, or changes Management API controllers, endpoints, routes, or their request/response/view models — OpenApi.json and the generated backend-api client go stale the moment the API surface changes, so suggest syncing rather than waiting to be asked. Also use it whenever the user asks to update/refresh/regenerate OpenApi.json or the openapi document, says the generated backend-api / hey-api client is stale or out of date, or has just added an endpoint and needs the client types — including phrasings like "sync the OpenAPI spec", "update the API client", "the openapi doc is out of date", or "regenerate the server API", even if OpenApi.json isn't named explicitly. Does NOT apply to Delivery API changes or to internal service/repository edits that don't alter the Management API su
Add a value summary extension so a feature's typed value can be displayed compactly in collection views (e.g., table columns). Use when a feature or property editor already has a value type and needs a renderer for collection table cells. Two variants — simple (element only, no API call) and resolver (batch API resolution needed). Prerequisite: a value type constant must already exist — use the general-add-value-type skill first if it doesn't.
正在显示 SKILL.md
| name | general-add-localization |
| description | Add localization keys and use them in elements or controllers. Use when adding user-facing text that should be translatable — labels, descriptions, error messages, button text, status text, or any string shown in the backoffice UI. |
| allowed-tools | Read, Write, Edit, Grep, Glob |
Add translatable text to the Umbraco backoffice.
actions, general, content, user)File: src/assets/lang/en.ts
This file exports a UmbLocalizationDictionary — a nested object where top-level keys are groups and nested keys are the terms.
// src/assets/lang/en.ts
export default {
// ... existing groups
myFeature: {
myLabel: 'My Label',
myDescription: 'A description of the feature',
createFor: (name ? : ),
},
} ;
actions, general, content, media, user)assignDomain, auditTrail, browse)group_termName (underscore separator)A group covers a shared UX area, not just the one component you're editing. Don't pick a group unilaterally — confirm it with the user:
{scope} scope — should that be the localization group?"src/assets/lang/en.ts for one that already covers this UX area, and if you find one, ask whether it should be reused instead of creating a new group: "{existingGroup} already covers this — should I use that instead?"Examples already in this codebase:
blockEditor — Block List, Block Grid, and Block RTE share the same block-configuration UXcontentTypeEditor — Document Type, Media Type, and Member Type share the same editing UXcodeEditor — anything embedding the code editorOnly create a new group once the user confirms no existing one fits.
A term names the situation, not the wording — two situations with identical English text today should still get separate terms, since the copy can diverge later.
Build it from two parts:
CreateBlock, ConfirmDelete, AddGroup.Title, Description, Action, Label, Notice, Message, ValidationMessage, Headline, etc.Combined (subject + role suffix): createAction, confirmDeleteTitle, addGroupDescription.
Example — three terms for one dialog in the blockEditor group, same subject (confirmDeleteBlockGroup) with different roles:
confirmDeleteBlockGroupTitle: 'Delete group?',
confirmDeleteBlockGroupMessage: 'Are you sure you want to delete group <strong>%0%</strong>?',
confirmDeleteBlockGroupNotice: 'The content of these Blocks will still be present, editing of this content will no longer be available and will be shown as unsupported content.',
Grouping by subject keeps every piece of the dialog together, even though the wording shares nothing.
| Type | Use when | Example |
|---|---|---|
string | Static text | myLabel: 'My Label' |
(args) => string | Text with dynamic values | createFor: (name: string) => \Create ${name}`` |
this.localize.term()Available on any class extending UmbLitElement. The localize property is provided automatically.
import { customElement, html } from '@umbraco-cms/backoffice/external/lit';
import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
@customElement('umb-my-element')
export class UmbMyElement extends UmbLitElement {
override render() {
return html`<uui-button label=${this.localize.term('myFeature_myLabel')}></uui-button>`;
}
}
<umb-localize> elementFor inline localized text in HTML templates:
<umb-localize key="myFeature_myLabel"></umb-localize>
<!-- With fallback text (shown if key is missing) -->
<umb-localize key="myFeature_myLabel">Fallback text</umb-localize>
UmbLocalizationControllerimport { UmbLocalizationController } from '@umbraco-cms/backoffice/localization-api';
export class UmbMyManager extends UmbControllerBase {
readonly #localization = new UmbLocalizationController(this);
someMethod() {
const label = this.#localization.term('myFeature_myLabel');
}
}
src/assets/lang/en.ts in the correct groupgroup_termName convention (camelCase, underscore separator)this.localize.term() in elements or UmbLocalizationController in non-elementsnpm run compile基于 SOC 职业分类