acp-translate

Align de/fr translation files to en.json for Adaptive Cover Pro.

151|23|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/jrhubott/adaptive-cover-pro --skill acp-translate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-translate
Source: https://github.com/jrhubott/adaptive-cover-pro/tree/main/.claude/skills/acp-translate
Command: npx skills add https://github.com/jrhubott/adaptive-cover-pro --skill acp-translate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs the translation files for Adaptive Cover Pro by ensuring en.json remains the source of truth and de/fr translations stay in sync, while providing a pathway to add new languages or remove unused ones.

Core Features & Use Cases

  • Source of truth: en.json is the single reference; all other language files must mirror its structure, including the services section.
  • Supported operations: Sync translations, Add language, Drop language, and Status checks to manage localization coverage.
  • Use case: Onboarding a new language like es, or updating translations after en.json changes, with automated validation.

Quick Start

Use this skill to align translations between en.json and a target language, or to add/drop a language.

Frequently Asked Questions about acp-translate

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

FAQPage Schema
How do I synchronize translation files when en.json changes in Home Assistant?

To synchronize translation files, run the Sync workflow to align de and fr language files with en.json, ensuring all translations mirror the source of truth structure including services. Automated validation confirms structural alignment across the Adaptive Cover Pro integration.

What is en.json's role in managing Home Assistant localization for custom integrations?

en.json serves as the single source of truth for localization. All other language files must mirror its exact structure, including services, so that translation validation and onboarding stay consistent across supported languages.

How do I add a new language like es to my existing translation files?

To add a new language, use the Add language workflow. The skill onboards the new language file by mirroring the en.json structure, including services, enabling you to populate translations with automated validation.

Does this translation validation support languages beyond de and fr?

Yes, translation validation supports adding or dropping any language. You can onboard new languages like es or remove unused ones using the Add language and Drop language workflows while enforcing en.json as the source.

How can I check the localization coverage status of my translation files?

To check localization coverage, use the Status workflow. It reviews the translation files against en.json to verify structural alignment and reports the current status of all supported languages, including missing services sections.

How do I remove an unused language from my integration's translation files?

To remove an unused language, run the Drop language workflow. This safely drops the target language file from the localization setup while preserving the en.json source of truth and remaining translation structures.