mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-20 12:23:22 +00:00
Claude Code keeps its per-project off list in ~/.claude.json, the same file its user-scope servers live in. The plan keyed desired entries by file path alone, so one file could carry only one native target, and mcp.projects had to refuse a disabled entry for Claude Code rather than write that list. Key the plan by file and target instead. Apply already rereads the file per plan, and sectionDigest hashes only the target's own section, so two plans on ~/.claude.json fold in order without further machinery. A change now carries the mcp.projects root it belongs to. Its path no longer says, because a project's off switch is written outside that project folder, and the dashboard needs the root to keep the switch out of the global server list and to show a pending badge on the project it came from. Codex stays refused. It merges the project file field by field, so a switch for a server its global config lacks leaves an entry with no transport and stops Codex loading its config at all. Alongside this, the dashboard gets a named "Turn off a global server" action, so adding a switch and adding a server are two choices up front rather than one form that asks afterwards. Two older glitches go with it: a project's target toggles sprang back while the list was still empty, and the expanded config editor stayed open when a tab arrived from the URL. Refs #286
Dashboard Translations
The dashboard uses one JSON file per locale in ui/src/i18n/locales/.
Files
en.jsonis the canonical source of keys.- Every other locale must contain exactly the same keys.
- Run the UI test suite after editing translations; the parity test checks missing keys, extra keys, and placeholder mismatches.
Key Style
- Use dot-separated keys grouped by area, for example
layout.nav.dashboardorapi.error.not_found. - Keep keys stable. Rename a key only when updating every locale and all call sites.
- Prefer reusable labels under
common.*only when the same text means the same thing in every context.
Tone
- Keep translations natural and conversational, as if they are product UI copy a user sees while working.
- Be concise. Labels should fit buttons, nav items, badges, and dialogs without wrapping awkwardly.
- Avoid stiff literal translations, internal engineering phrasing, jokes, and slang.
- For errors, explain what happened in plain language. Keep raw technical details in placeholders or fallback text.
Placeholders
- Use named placeholders with braces:
Updated {name}. - Placeholder names must match across every locale.
- Do not translate placeholder names.
Do Not Translate
- Product and command names such as
skillshare,skillshare ui, Git, and CodeMirror. - User-owned data: file paths, skill names, repo names, branch names, commit messages, audit rule messages, and terminal output.
- API codes such as
target.not_found; translate the text mapped to those codes instead.