From devflow
Set DevFlow language preference — all responses, hook messages, and interactions switch to the selected language
npx claudepluginhub nexuz-sys/devflow --plugin devflowThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Processes code review feedback technically: verify suggestions against codebase, clarify unclear items, push back if questionable, implement after evaluation—not blind agreement.
/devflow languageDisplay this interactive menu:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
DevFlow — Language / Idioma / Idioma
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Select your preferred language:
1. 🇺🇸 English
2. 🇧🇷 Português (Brasil)
3. 🇪🇸 Español
Current: {current_language}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If the user provided the language directly (e.g., /devflow language pt-BR or /devflow language português), skip the menu and go to Step 2.
Language code mapping:
1, en, en-US, english, inglês, inglés → en-US2, pt, pt-BR, português, portugues, portuguese → pt-BR3, es, es-ES, español, espanol, spanish → es-ESAfter the user selects a language, save the preference file:
Project-level (recommended — each project can have its own language):
echo "LANGUAGE_CODE" > .devflow-language
User-level (global fallback for all projects):
echo "LANGUAGE_CODE" > ~/.devflow-language
Ask the user which scope they prefer. Default to project-level if they don't specify.
The file contains just the language code (e.g., pt-BR), no other content.
After saving the preference file, propagate the language to integrated tools:
The dotcontext CLI accepts --lang <locale> as a global flag. Update .mcp.json to pass the language to the MCP server:
# Read current .mcp.json and update the dotcontext args to include --lang
Use python3 to update the .mcp.json:
import json
mcp_path = ".mcp.json"
with open(mcp_path) as f:
config = json.load(f)
if "dotcontext" in config.get("mcpServers", {}):
args = config["mcpServers"]["dotcontext"]["args"]
# Remove existing --lang/-l flags
new_args = []
skip_next = False
for i, arg in enumerate(args):
if skip_next:
skip_next = False
continue
if arg in ("--lang", "-l"):
skip_next = True
continue
new_args.append(arg)
# Add --lang before "mcp" subcommand
mcp_idx = new_args.index("mcp") if "mcp" in new_args else len(new_args)
new_args.insert(mcp_idx, LANGUAGE_CODE)
new_args.insert(mcp_idx, "--lang")
config["mcpServers"]["dotcontext"]["args"] = new_args
with open(mcp_path, "w") as f:
json.dump(config, f, indent=2)
Map DevFlow locale codes to dotcontext locale codes:
en-US → enpt-BR → pt-BRes-ES → esImportant: After updating .mcp.json, inform the user that the dotcontext MCP server language will take effect on the next session restart.
Superpowers does not have a dedicated language configuration. However, the language instruction injected by the SessionStart hook already controls the LLM's response language, which covers all superpowers skill interactions. No additional propagation needed.
After saving, immediately switch your conversation language to the selected one. Confirm in the new language:
From this point forward in the current conversation, respond in the selected language. The hook messages (session-start, post-compact, etc.) will switch automatically on the next session start.
User runs /devflow language:
→ Show the menu, wait for selection, save .devflow-language, confirm in new language
User says "fale em português":
→ Detect intent, save pt-BR to .devflow-language, confirm in Portuguese, continue in Portuguese
User runs /devflow language es:
→ Skip menu, save es-ES, confirm: "Idioma configurado a Español..."
.devflow-language file is just a locale code string (e.g., en-US), one line, no whitespace.devflow-language in project root) overrides user-level (~/.devflow-language)en-US, pt-BR, es-ES (extensible via locales/ directory)locales/{code}/messages.sh — the framework picks it up automatically