/carbon-localization
Find localization blockers and contextually incorrect translations with CARBON.
Lucia · LocalizationExperience & accessibilityWhen to use it
Translations exist but may be wrong in product context.
Before you start
Provide source and target locales plus the real action behind each string. Inspect semantic reversals, terminology, plurals, placeholders and truncation. Escalate uncertain linguistic judgments to a qualified reviewer.
Try this in your coding agent.
/carbon-localization Review the Spanish checkout copy for meaning, context and truncation.Replace sample paths with your project. Slash names are shorthand; your host may use a plugin prefix or a skill picker. Invocation help →
ILLUSTRATIVE WALKTHROUGH
Spanish checkout
An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.
- 01Read context
- 02Investigate
- 03Show evidence
- 04Report
Coding-agent conversation
I’m reviewing spanish checkout. I’ll keep the scope and permissions explicit.
Follow the weakest evidence link and record what remains blocked.
Here is the evidence trail to inspect: Compare source intent, Spanish label and the action triggered; inspect truncation.
The translated action describes saving rather than placing an order. A native-language reviewer should validate final copy.
Example report
Illustration
TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.
- User intent
- Visible content
- Meaning / consistency
Illustrated outcome
The translated action describes saving rather than placing an order.
Evidence to inspect
Compare source intent, Spanish label and the action triggered; inspect truncation.
Still untested / not established
A native-language reviewer should validate final copy.
Ready. Read the full example or play its steps.
What a useful result contains
A bounded claim
For spanish checkout, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.
An inspectable trail
Compare source intent, Spanish label and the action triggered; inspect truncation. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.
The qualification
A native-language reviewer should validate final copy.
The next decision
Decide whether the evidence calls for a focused check, a reviewed fix or more context. Do not convert a plausible example into a verified finding.
Adapt the example to your project
- Replace spanish checkout with a real feature, path or decision in your project.
- State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
- Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-localization result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.Where to go next
/carbon-intl →/carbon-content →Content checked against the local command definition: skills/carbon-localization/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.