language-enforcement

Enforce Japanese output for user-facing content with rule hierarchy and glossary.

2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill language-enforcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: language-enforcement
Source: https://github.com/MysMon/Spec-Workflow-Toolkit/tree/main/skills/core/language-enforcement
Command: npx skills add https://github.com/MysMon/Spec-Workflow-Toolkit --skill language-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces Japanese language output for all user-facing content while maintaining code readability.

Core Features & Use Cases

  • Enforces hard language rules (MUST) that all responses are in Japanese.
  • Provides a rule hierarchy and a mapping glossary to ensure consistent terminology and messaging.
  • Guides validation and integration with other skills to maintain language consistency across workflows.

Quick Start

Enable Japanese-language enforcement by activating this skill in your workspace to ensure all subsequent outputs are generated in Japanese.

Frequently Asked Questions about language-enforcement

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

FAQPage Schema
How do I enforce Japanese output for all user-facing content?

Japanese output enforcement applies hard MUST rules demanding all responses in Japanese, covering documentation, specifications, product prompts, and error messages across workflows requiring language consistency.

What's the best way to maintain Japanese terminology consistency in localized documentation?

Maintaining Japanese terminology consistency relies on a rule hierarchy and a mapping glossary, which provide soft SHOULD rules for terminology and readability to ensure consistent messaging across content.

Does the Japanese language enforcement skill work with other workflow skills?

Yes, it provides integration guidance for other skills and includes a validation checklist to verify that Japanese language consistency is maintained across all connected workflows.

Can I keep code readable while enforcing Japanese responses for error messages and prompts?

Yes, the skill enforces Japanese output for all user-facing content while explicitly maintaining code readability, applying its hard and soft rules only to documentation, prompts, and messages.

When do I need to apply hard MUST rules versus soft SHOULD rules for Japanese localization?

Hard MUST rules demand all responses are generated in Japanese, while soft SHOULD rules govern terminology mapping and readability, creating a hierarchy that ensures consistent localized output.