Language Selection

Set and propagate user language preferences across DevFlow projects and sessions.

1|Updated Mar 27, 2026

Search Tags:#hooks #localization #language #i18n #multilingual #devflow #language-selection

Ready to run

npx skills add https://github.com/NEXUZ-SYS/devflow --skill language-selection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Language Selection
Source: https://github.com/NEXUZ-SYS/devflow/tree/main/skills/language
Command: npx skills add https://github.com/NEXUZ-SYS/devflow --skill language-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DevFlow users often want responses and hook messages in their preferred language. This Skill lets you set and propagate language preferences across the toolchain.

Core Features & Use Cases

Interactive language menu to choose en-US, pt-BR, or es-ES.
Persist language at project or user level (.devflow-language or ~/.devflow-language).
Propagate language to dotcontext MCP and the session hooks for consistent multilingual interactions.
Use Case: a multilingual team can collaborate in their native language while maintaining consistent DevFlow behavior.

Quick Start

Run the /devflow language command to select your preferred language and apply the setting immediately.

Frequently Asked Questions about Language Selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set the localization language for DevFlow interactions and hooks?▼

To set the localization language for DevFlow, run the /devflow language command to choose from interactive options like en-US, pt-BR, or es-ES. The preference is then applied immediately to all responses and session hooks.

Can I persist multilingual settings per project instead of per user?▼

Yes, you can persist multilingual settings at the project level using a .devflow-language file. Alternatively, setting it at the user level creates a ~/.devflow-language file in your home directory for global interactions.

How does i18n preference propagation work with dotcontext MCP?▼

I18n preference propagation works by updating dotcontext MCP args with the proper locale codes. This ensures that the dotcontext integration and session hooks adhere to your chosen locale across the entire DevFlow ecosystem.

What is the best way to maintain consistent multilingual behavior in a development team?▼

The best way to maintain consistent multilingual behavior is to set a project-level language file (.devflow-language). This ensures all team members collaborate in the configured native language while maintaining uniform DevFlow behavior.

Do I need to manually update session hooks when changing my DevFlow language?▼

No, you do not need to manually update session hooks when changing your DevFlow language. The Skill automatically propagates your preference to the session hooks and dotcontext MCP upon selection.