ux-copy-ja-review

Review Japanese UX copy in Markdown tables for style guide and terminology compliance.

1|Updated May 21, 2020
One-click install
npx skills add https://github.com/ahandsel/debugging_log --skill ux-copy-ja-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-copy-ja-review
Source: https://github.com/ahandsel/debugging_log/tree/main/skills/ux-copy-ja-review
Command: npx skills add https://github.com/ahandsel/debugging_log --skill ux-copy-ja-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses inconsistencies and grammatical errors in Japanese UI copy, ensuring that error messages, labels, and helper text adhere to strict project style guides and terminology standards.

Core Features & Use Cases

  • Style Compliance: Automatically checks Japanese copy against established project style guides and component-specific rules.
  • Terminology Enforcement: Validates that UI text uses approved terms from the project glossary, preventing confusion.
  • Use Case: When updating a dashboard, use this skill to review a Markdown table of new error messages to ensure they follow the correct honorific levels, punctuation rules, and terminology for the specific UI component.

Quick Start

Use the ux-copy-ja-review skill to analyze the Japanese copy in the file tasks-kinid/v1-midfi/prd37-pw-mgt.md for style and terminology compliance.

Frequently Asked Questions about ux-copy-ja-review

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

FAQPage Schema
How do I review Japanese UX copy for style guide and terminology compliance?

To review Japanese UX copy for style guide compliance, input Markdown tables containing UI text alongside project-specific style guides and terminology CSV files to validate grammatical conventions and approved terms.

What is the best way to standardize Japanese error messages in UI text?

Standardizing Japanese error messages in UI text requires checking the copy against project-specific style guides and component guidelines to ensure correct honorific levels, punctuation, and terminology.

Do I need terminology CSV files to validate Japanese localization?

Yes, validating Japanese localization requires access to project-specific terminology CSV files, style guides, and component guidelines to accurately enforce approved UI text and grammatical conventions.

Can I check Markdown tables for Japanese UI text consistency automatically?

Yes, you can automatically check Markdown tables for Japanese UI text consistency by applying the review process to validate copy against established component-specific rules and project glossaries.

Why does my Japanese UI copy fail style compliance checks?

Japanese UI copy fails style compliance checks when error messages, labels, and helper text contain inconsistencies, incorrect honorific levels, or unapproved terms that deviate from the project glossary.

Are there limitations when using this approach for Japanese copy review?

A limitation of this Japanese copy review approach is its dependency on pre-existing project-specific style guides and terminology CSV files; without these inputs, accurate linguistic validation cannot be performed.