skills.rest
ahandsel
ahandselCOMMUNITY
Explore all skills by this author →
GitHub

ux-key-searcher

Match highlighted UX copy in Markdown tables against CSV phrase files to populate translation key metadata.

1|Updated May 21, 2020
Search Tags:#automation#markdown#localization#copywriting#csv#ux
One-click install
npx skills add https://github.com/ahandsel/debugging_log --skill ux-key-searcher
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-key-searcher
Source: https://github.com/ahandsel/debugging_log/tree/main/skills/ux-key-searcher
Command: npx skills add https://github.com/ahandsel/debugging_log --skill ux-key-searcher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual effort of searching through CSV files to find existing translation keys for UX copy, ensuring consistency and preventing the creation of duplicate keys.

Core Features & Use Cases

  • Exact Match Search: Automatically scans phrase-data CSV files for exact matches of English or Japanese UX copy.
  • In-place Table Updates: Updates Markdown tables directly by filling in key names, descriptions, and status notes.
  • Context-Aware Matching: Uses project and key-prefix heuristics to resolve ambiguous matches when multiple candidates exist.

Quick Start

Highlight the table containing your UX copy and ask the assistant to search for existing keys using the ux-key-searcher skill.

Frequently Asked Questions about ux-key-searcher

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

FAQPage Schema
How do I find existing translation keys for UX copy in a CSV file?▼

To find existing translation keys for UX copy, you can match text against project-specific CSV phrase files to identify exact English or Japanese matches and populate key metadata in-place. This prevents the creation of duplicate translation keys.

Can I automatically update Markdown tables with translation key metadata?▼

You can automatically update Markdown tables by matching highlighted UX copy against CSV data to fill in key names, descriptions, and status notes directly in-place. This eliminates manual searches through phrase files.

Do I need Node.js to search CSV files for localization keys?▼

Node.js is required to execute the search helper and process CSV data structures accurately when matching UX copy. The runtime ensures the localization search helper functions correctly.

How does context-aware matching resolve ambiguous UX copy in localization files?▼

Context-aware matching resolves ambiguous UX copy by using project and key-prefix heuristics to evaluate multiple candidates within the localization files. This ensures the correct existing translation key is selected.

What is the best way to prevent duplicate translation keys for English and Japanese text?▼

The best way to prevent duplicate translation keys is to automatically scan English and Japanese text columns in CSV phrase files for exact matches before assigning new keys. This maintains localization consistency.

Are there limitations when mapping UX copy to existing design keys in Markdown?▼

A limitation when mapping UX copy is that the process requires structured Markdown tables and project-specific CSV files with English or Japanese text columns to function accurately. Ambiguous matches rely on predefined key-prefix heuristics.

Related Skills

Explore More Design & Creative Skills→
ahandselahandsel
1

ux-en-to-ja-localize

Localize English UX copy to Japanese in Phrase CSV files with key-based updates.

Community
Advanced
pixel-cellarpixel-cellar
277

localize

Scan source code, extract localization strings, and validate translations.

Official
Advanced
ahandselahandsel
1

ux-task-to-phrase

Synchronize pending UX copy from Markdown task files into Phrase localization CSVs.

Community
Advanced
hiyeshuhiyeshu
4

localize

Extract static text and synchronize translation files across languages.

Community
Intermediate