Proposal: Localization / language-pack support for gstack skills (starting with Traditional Chinese)

[howardpen9]

Summary

gstack is an incredible workflow framework, and its adoption is growing fast globally. As non-English-speaking developers discover it, a localization layer would significantly lower the barrier to entry — especially for the README and quickstart guide, which are the first touchpoint.

This proposal starts small: a translated README (Traditional Chinese / zh-TW) placed alongside the original, with a lightweight convention that could scale to other languages.

Why this matters

• gstack's skills use role-based prompts (CEO, Designer, QA Lead, etc.). Understanding what each role does is critical for first-time users. A localized overview helps non-native English speakers get started faster.
• The README is the single most important onboarding document. A zh-TW version lets the Chinese-speaking developer community (one of the largest on GitHub) understand gstack's value proposition immediately.
• This does not touch any skill logic, templates, or generated files. Zero risk to the existing English-first workflow.

Proposed scope (minimal)

1. Add docs/zh-TW/README.md — a human-quality Traditional Chinese translation of the main README
2. Add a small "🌐 Languages" section near the top of the root README linking to available translations
3. Convention: docs/{locale}/ for future translations (e.g., ja, ko, zh-CN)

What this does NOT do

• Does not translate SKILL.md files (they're generated from .tmpl and consumed by AI agents — translating them would be counterproductive)
• Does not add any i18n framework or runtime dependency
• Does not change any existing file behavior

Next steps

If the maintainers are open to this direction, I'm happy to submit a PR with the zh-TW README translation. Happy to follow any formatting or structural guidelines you prefer.

[garrytan]

Thanks @howardpen9 — closing as a duplicate of #481 (locale-aware localization). zh-CN docs also landed via #1371. Continue the discussion on #481 if you want to push the broader proposal forward.