Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bastndev/f1/llms.txt

Use this file to discover all available pages before exploring further.

F1 ships with a fully translated interface for 12 locales, covering both the extension’s static identity strings and its runtime notification messages. VS Code automatically selects the correct locale based on your editor’s display language setting — no manual configuration is required. The two i18n mechanisms complement each other and together ensure every user-facing string appears in their language from the moment the extension loads.

How Localization Works

F1 uses both of VS Code’s built-in i18n systems simultaneously.

1. package.nls.*.json — Identity Strings

The package.nls.json file at the repository root contains the default (English) values for %placeholder% tokens referenced in package.json, including displayName and description. For every supported non-English locale there is a corresponding package.nls.<locale>.json file (e.g. package.nls.es.json, package.nls.zh-cn.json). VS Code reads these files before the extension activates, so the extension’s name and description appear in the correct language in the Extensions view, search results, and marketplace listings without any runtime cost.
// package.nls.json (English default)
{
  "displayName": "F1",
  "description": "All-in-One (F1 [AI] composer) — [CLI Hub, My skills, My Memory] ..."
}

2. l10n/bundle.l10n.*.json — Runtime Notifications

Runtime strings — such as showInformationMessage dialogs, modal prompts, and button labels — are stored in l10n/bundle.l10n.<locale>.json files inside the l10n/ directory. These are loaded on demand by VS Code’s vscode.l10n API. Call sites in the extension use vscode.l10n.t("English text") to look up the translated string at runtime:
const install = vscode.l10n.t('Install');
const choice = await vscode.window.showInformationMessage(
  vscode.l10n.t(
    'Get smarter keybindings for AI tools — Lynx Keymap adds optimized shortcuts for Claude, Cursor, Copilot and more.'
  ),
  install
);
The "l10n": "./l10n" field in package.json tells VS Code where to find these runtime bundles:
// package.json (excerpt)
{
  "l10n": "./l10n"
}
The Prompt Composer’s 5-language source picker (English, Spanish, Chinese, Portuguese, Russian) is a separate feature from the UI locale. It controls which language you write prompts in and auto-translates them to English before sending — it operates independently of your VS Code display language.

Supported Locales

F1 ships translations for 12 locales. English is the built-in default; the remaining 11 locales have both package.nls.<locale>.json identity files and l10n/bundle.l10n.<locale>.json runtime bundles.
LanguageLocale CodeFlag
Englishen🇺🇸
Spanishes🇪🇸
Chinese (Simplified)zh-cn🇨🇳
Germande🇩🇪
Frenchfr🇫🇷
Japaneseja🇯🇵
Koreanko🇰🇷
Portuguese (Brazil)pt-br🇧🇷
Russianru🇷🇺
Vietnamesevi🇻🇳
Hindihi🇮🇳
Arabicar🇸🇦

Repository Layout

The localization files live at the root level and in the l10n/ directory:
F1/
├── package.nls.json            # English identity (default)
├── package.nls.ar.json         # Arabic identity
├── package.nls.de.json         # German identity
├── package.nls.es.json         # Spanish identity
├── package.nls.fr.json         # French identity
├── package.nls.hi.json         # Hindi identity
├── package.nls.ja.json         # Japanese identity
├── package.nls.ko.json         # Korean identity
├── package.nls.pt-br.json      # Portuguese (Brazil) identity
├── package.nls.ru.json         # Russian identity
├── package.nls.vi.json         # Vietnamese identity
├── package.nls.zh-cn.json      # Chinese (Simplified) identity
└── l10n/
    ├── bundle.l10n.ar.json     # Arabic runtime strings
    ├── bundle.l10n.de.json     # German runtime strings
    ├── bundle.l10n.es.json     # Spanish runtime strings
    ├── bundle.l10n.fr.json     # French runtime strings
    ├── bundle.l10n.hi.json     # Hindi runtime strings
    ├── bundle.l10n.ja.json     # Japanese runtime strings
    ├── bundle.l10n.ko.json     # Korean runtime strings
    ├── bundle.l10n.pt-br.json  # Portuguese (Brazil) runtime strings
    ├── bundle.l10n.ru.json     # Russian runtime strings
    ├── bundle.l10n.vi.json     # Vietnamese runtime strings
    └── bundle.l10n.zh-cn.json  # Chinese (Simplified) runtime strings
To change the locale F1 uses, change your VS Code display language via Command Palette → Configure Display Language and restart the editor. VS Code will automatically select the matching package.nls and l10n bundle files.

Build docs developers (and LLMs) love