菜单
Adding, changing, or translating user-facing strings in NinerLog (i18next, EN + DE namespaces). Load whenever you write text a user will see, add a translation namespace, hit the CI translation-completeness check, or need to keep en/de locale files in sync.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/fjaeckel/ninerlog-frontend --skill i18n命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Regenerate the marketing feature images and demo clips used by ninerlog.com and the ninerlog deployment README — light+dark stills and WebM/GIF animations rendered from the app against the "famous women in aviation" story fixtures. Load when asked to refresh website/README screenshots, add a marketing shot for a new feature, or change the demo story.
How NinerLog talks to its backend — regenerating the typed client from the OpenAPI spec, writing TanStack Query hooks, cache invalidation, and the auth/token-refresh machinery. Load when adding or changing an API-backed hook, consuming a new endpoint, regenerating src/api/schema.ts, debugging 401s/token refresh/session resume, or fixing stale data after a mutation.
House comment style — every comment is terse and states only the WHAT, never the WHY. Rationale, history, and justification live in git commit messages and documentation, not in source. Load before writing any comment, when touching code that contains comments, when reviewing a diff, or when auditing a file or component for comment style.
基于 SOC 职业分类
正在显示 SKILL.md
| name | i18n |
| description | Adding, changing, or translating user-facing strings in NinerLog (i18next, EN + DE namespaces). Load whenever you write text a user will see, add a translation namespace, hit the CI translation-completeness check, or need to keep en/de locale files in sync. |
All user-facing text is translated. NinerLog ships English and German. Translations are namespaced — one JSON per feature area under src/i18n/locales/<lang>/.
Namespaces: common auth nav flights aircraft dashboard currency licenses credentials reports settings import help backups onboarding quicklog signatures.
import { useTranslation } from 'react-i18next';
const { t } = useTranslation('flights'); // pick the namespace
return <button className="btn-primary">{t('addFlight')}</button>;
Cross-namespace access uses the prefixed form: t('common:save').
en must be added to de in the same file. .github/workflows/i18n-check.yml diffs leaf keys with jq and fails the build on any key present in EN but missing in DE. (DE-only keys are a warning, not a failure.)localStorage under ninerlog-language; fallback is English.A new JSON file is not enough — register it in src/i18n/index.ts:
import enFoo from './locales/en/foo.json'; and the de counterpart.foo: enFoo / foo: deFoo under the respective resources entries.'foo' to the ns array.for f in src/i18n/locales/en/*.json; do
ns=$(basename "$f")
diff <(jq -r '[paths(scalars)|join(".")]|sort[]' "$f") \
<(jq -r '[paths(scalars)|join(".")]|sort[]' "src/i18n/locales/de/$ns") \
>/dev/null || echo "drift in $ns"
done
Aviation terminology stays in the form German-speaking pilots actually use — keep established English abbreviations (PIC, IFR, VFR, PPL, ATPL, METAR) untranslated, and prefer the term from the EASA German-language forms over a literal translation. Match the tone of neighbouring keys; the UI addresses the user informally but not chattily. See docs/TRANSLATION_GUIDE.md.