campfire: Skill for Claude Code

Adding a language to Campfire

One language per run. Everything below is required; a language missing any step is broken somewhere (a "???" string, English system dialogs on iOS, an English loading screen on the web, a docs list that forgets it). The checklist is enforced by scripts/language.py; run it, never skip it.

Romanian (ro) was added this way and is the worked example: when unsure how a step looks, look at how ro appears in that file. Don't commit unless the user asks (then load the commit-messages skill). Load the code-style skill before editing any .kt or strings.xml file.

L=.claude/skills/add-language/scripts/language.py below.

1. Ask for the language

If the request names no language, ask for one (AskUserQuestion, or a plain question). If it names several, take the first, say the others need a run each, and carry on with that one only.

Settle these names now and use them everywhere:

Name	Rule	Romanian
code	ISO 639-1 (639-2 only if no 639-1), lowercase, no region	ro
English name	as English writes it	Romanian
enum entry	English name, upper snake case	ROMANIAN
key suffix	English name, lower snake case	romanian
own name	the language's name for itself, capitalized as a picker shows it	Română
strings object	Strings + code capitalized (generated by the plugin)	StringsRo

2. Preflight: stop if the language needs groundwork

Write a sample with every letter of the language's alphabet in both cases, every diacritic, its quotation marks, and any punctuation of its own, then run:

python3 $L preflight <code> --sample "<sample>"

• Exit 2 (ABORT lines): stop. Make no changes. Tell the user that <Language> needs groundwork before it can be added, quoting each ABORT line, and what that groundwork is:
  • fonts: Inter and JetBrains Mono hold Latin, Greek, and Cyrillic, and ui/theme/ScriptFaces.kt one row per other script (Hebrew so far). A script no row covers needs a row there, its face subset by tools/fonts/script_faces.py, and credited (root CLAUDE.md → Build).
  • plurals: localization/PluralRules.kt has no row for the language; its CLDR cardinal rule goes there first, with a test.
  • code: a regional variant, or a retired code (iw): the language is added under the code LanguageCodes folds to, which also maps what Android reports.
• NOTE lines: carry on, keep them for step 5's brief and the final report. A language written from the right gets a NOTE with its checklist (the AppLanguage direction in step 3, dir in step 3's web block, the stores' codes in step 8); everything else about RTL (layout, songs, the editor, the PDF) follows from the direction.
• Exit 0: carry on.