Gdd Locale logo

Gdd Locale

Community
hegemonart
gdd-locale

Inspects or sets the GDD CLI locale for this project. With no argument, reports the resolved locale (config.locale > env LANG > en), the fallback chain, and per-locale coverage (which message tables are complete vs placeholder). With a <code> (en/ru/uk/de/fr/zh/ja), sets .design/config.json#locale after previewing the change. Localizes --help, common error messages, and skill prompt headers via scripts/lib/i18n/; missing keys fall back to English, so a partial locale never breaks the CLI. Use to switch GDD's own output language.

Overview

Publisherhegemonart
Repositoryget-design-done
Skill namegdd-locale
Stars
3
Forks
1
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by hegemonart on GitHub. Read the source before you install it.

Installation

Install the Gdd Locale AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/locale
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/hegemonart/get-design-done.git /tmp/get-design-done
mkdir -p .claude/skills
cp -r /tmp/get-design-done/scripts/skill-templates/locale .claude/skills/gdd-locale
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gdd Locale in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gdd Locale on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gdd Locale is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

{{command_prefix}}locale

Closes the English-only CLI gap: GDD's README is multilingual, but --help, errors, and skill prompt headers spoke English until now. This skill inspects or sets the project's locale. Contract: ../../reference/cli-localization.md.

Invocation

CommandBehavior
{{command_prefix}}localeReport the resolved locale, the fallback chain, and per-locale coverage.
{{command_prefix}}locale <code>Set .design/config.json#locale to <code> (en/ru/uk/de/fr/zh/ja), after preview.

Steps

  1. Resolve current. Read .design/config.json#locale (if any) and the environment, then call the resolver to report the active locale + chain:

    bash
    node -e '
      const i = require("./scripts/lib/i18n/index.cjs");
      let cfg = {}; try { cfg = JSON.parse(require("fs").readFileSync(".design/config.json","utf8")); } catch {}
      const loc = i.resolveLocale({ env: process.env, configLocale: cfg.locale });
      const cov = i.KNOWN_LOCALES.map((l) => `${l}:${(i.loadTable(l)._meta||{}).coverage||"?"}`).join("  ");
      console.log(JSON.stringify({ resolved: loc, chain: i.fallbackChain(loc), coverage: cov }));
    '
  2. No argument → print the resolved locale, the fallback chain, and the coverage line (which tables are complete vs placeholder). Stop.

  3. <code> argument → validate it is in KNOWN_LOCALES (en/ru/uk/de/fr/zh/ja). Unknown → print the error.invalid_locale message + the known list, change nothing.

  4. Preview + set. Show locale: <old> -> <code>, then write locale into .design/config.json (create the file if absent, preserving any existing keys). Confirm, and note that missing keys in a placeholder locale fall back to English.

Output

End with:

## LOCALE COMPLETE

Frequently asked questions

What does the Gdd Locale AI skill do?

Inspects or sets the GDD CLI locale for this project. With no argument, reports the resolved locale (config.locale > env LANG > en), the fallback chain, and per-locale coverage (which message tables are complete vs placeholder). With a <code> (en/ru/uk/de/fr/zh/ja), sets .design/config.json#locale after previewing the change. Localizes --help, common error messages, and skill prompt headers via scripts/lib/i18n/; missing keys fall back to English, so a partial locale never breaks the CLI. Use to switch GDD's own output language.

Why use Gdd Locale on TypingMind?

Because you install it once and use it with any model. Gdd Locale is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gdd Locale in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hegemonart/get-design-done/tree/main/scripts/skill-templates/locale. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Gdd Locale?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gdd Locale?

As many as you like. As long as a model supports skills, you can use Gdd Locale with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gdd Locale AI skill free?

Yes. It is published on GitHub by hegemonart under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇