CARBON — Engineering ConfidenceUser Guide
CHAPTER 17 / 60 Pro

/carbon-intl

Assess an app's internationalization (INTL/i18n) readiness and completion against intended locales and markets. Inspect architecture, string externalization, locale handling, formatting, Unicode, RTL, testing and delivery gaps; produce a branded readiness report.

Lucia · LocalizationExperience & accessibility

When to use it

You are preparing the architecture for more markets.

Before you start

List intended locales and inspect externalized strings, Unicode, currencies, dates, text expansion and direction. A readiness matrix should separate implementation gaps from verified runtime behavior.

Try this in your coding agent.

/carbon-intl Review src/checkout for hard-coded currency, dates and text-direction assumptions.

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

Currency and direction readiness

An expanded teaching example, not a recorded or live execution. The report stays visible while the replay explains how to read it.

  1. 01Read context
  2. 02Investigate
  3. 03Show evidence
  4. 04Report

Coding-agent conversation

Read context

I’m reviewing currency and direction readiness. I’ll keep the scope and permissions explicit.

Investigate

Follow the weakest evidence link and record what remains blocked.

Show evidence

Here is the evidence trail to inspect: Source: "$" + amount → review currency and RTL layout assumptions.

Report

A dollar sign is embedded in the component instead of locale formatting. No claim that all locales were executed.

CARBON

Example report

Illustration
Meaning, price and presentation
Meaning, price and presentation — TestBucks teaching screen

TestBucks course screen with illustrative analysis. The screenshot supplies context; the demo does not establish a newly observed bug.

  1. User intent
  2. Visible content
  3. Meaning / consistency

Illustrated outcome

A dollar sign is embedded in the component instead of locale formatting.

Evidence to inspect

Source: "$" + amount → review currency and RTL layout assumptions.

Still untested / not established

No claim that all locales were executed.

Ready. Read the full example or play its steps.

What a useful result contains

A bounded claim

For currency and direction readiness, state the target, revision, environment and actual work performed. Keep planned, executed, blocked and untested work separate.

An inspectable trail

Source: "$" + amount → review currency and RTL layout assumptions. In a real run, retain the source, trace, screenshot or fixture behind the conclusion.

The qualification

No claim that all locales were executed.

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

  1. Replace currency and direction readiness with a real feature, path or decision in your project.
  2. State the expected rule and its source. Include safe fixtures, constraints and a budget where appropriate.
  3. Ask for exact evidence and remaining gaps. Approve consequential actions separately.
/jay Review the /carbon-intl result. Separate observed evidence, assumptions and untested scope, then recommend the next useful check.

Where to go next

/carbon-localization →/carbon-compatibility →

Content checked against the local command definition: skills/carbon-intl/SKILL.md. Examples adapted from the homepage’s TestBucks walkthroughs. Availability is edition- and host-dependent.