用語・表記ガイドライン

Standardize Japanese terminology and Katakana usage across code, documentation, and UI.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Takashi-Matsumura/box-frame --skill -takashi-matsumura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 用語・表記ガイドライン
Source: https://github.com/Takashi-Matsumura/box-frame/tree/main/.claude/skills/terminology
Command: npx skills add https://github.com/Takashi-Matsumura/box-frame --skill -takashi-matsumura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Japanese terminology and Katakana usage to ensure consistent language across code, documentation, and UI.

Core Features & Use Cases

  • Terminology standardization: Aligns on preferred forms across code, docs, and UI.
  • Guided translation and UI wording: Provides rules for translations and UI text to improve clarity and UX.
  • Use Case: When collaborating on a Japanese product, apply these guidelines to maintain consistent wording in software messages and developer docs.

Quick Start

Apply the terminology guidelines to new UI strings and documentation by referencing the frontmatter's description and the examples within this Skill.

Frequently Asked Questions about 用語・表記ガイドライン

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

FAQPage Schema
How do I standardize Japanese terminology across code, documentation, and UI?

You standardize Japanese terminology by applying explicit guidelines that align preferred word forms and Katakana usage across software projects. This Skill enforces consistent language rules so teams maintain unified wording in code, docs, and UI strings.

What is the best way to unify Katakana usage in Japanese software documentation?

Unifying Katakana usage in Japanese documentation involves referencing enforced terminology guidelines and practical examples. This Skill provides standardized rules for translations and UI text to ensure consistent Katakana wording across developer docs and software messages.

When do I need terminology standardization for a Japanese product?

Terminology standardization is needed when collaborating on a Japanese product requiring consistent wording across software messages and developer docs. It ensures multilingual or Japanese-focused teams align on preferred Katakana forms and UI text to improve clarity and UX.

Does this terminology guideline work for both UI wording and code generation?

Yes, the terminology guideline works for UI wording, code generation, and documentation creation. It applies explicit terminology rules across all software project areas, ensuring unified Japanese language and Katakana usage in generated code strings and UI text.

How do I apply unified terminology terms to new UI strings?

You apply unified terminology terms to new UI strings by referencing the Skill's frontmatter description and embedded examples. These provide explicit guidelines and quick-start steps to ensure consistent Japanese wording in software interfaces and documentation.