i18n-check

Included with Lifetime

$97 forever

Analyze code for internationalization issues, understanding the UI context and user impact before flagging problems. Use when reviewing code for global readiness.

Design

What this skill does


# i18n Check

Analyze code for internationalization issues, with emphasis on understanding impact and user experience.

## Philosophy

This is not about flagging every hardcoded string. It's about asking:

> "If someone in Cairo, Munich, or Tokyo uses this, will it work for them?"

i18n issues aren't just bugs—they're barriers. A date shown as "12/05/2024" is ambiguous to most of the world. A text field that truncates German words breaks the experience. A layout that assumes left-to-right excludes 400 million RTL readers.

## Scope

The user may specify a file path, glob pattern, or directory. If not specified, ask what they'd like to check.

## Config Integration

Before starting, follow the migration preflight in `references/config-migration.md`, then read `.assistant-config.md` from the project root.

If it exists:
1. **Read** scope decisions and acknowledged findings
2. **If i18n is "out of scope"**: Skip the check entirely, output brief note:
   ```
   ## i18n Analysis: [path]

   **Skipped:** i18n checks disabled per project config (US-only)
   To re-enable, update .assistant-config.md
   ```
3. **If in scope**: Skip acknowledged findings, note them in output
4. **Note** at the top of output: "Config loaded: .assistant-config.md"

## Process

### 1. Read and Understand

First, **read the code** to understand:
- What does this component/file do?
- Is this user-facing or internal tooling?
- What kind of content does it display? (dates, numbers, text, forms)
- Is there existing i18n infrastructure? (react-intl, i18next, etc.)

### 2. Trace the User Experience

Think through what users see:
- Where do dates/times appear? How are they formatted?
- Where does text appear? Can it expand without breaking?
- What direction does the layout assume?
- What do forms ask for? Are fields US-specific?

### 3. Assess Impact by Audience

**Critical** (breaks functionality):
- Date formats that cause confusion (12/05 - December 5 or May 12?)
- Forms that require US-only fields (State, ZIP) with no alternatives
- Layouts completely broken in RTL

**Serious** (degraded experience):
- Text truncated due to expansion
- Currency/number formats that look wrong
- Hardcoded strings that can't be translated

**Minor** (suboptimal):
- Missing locale parameter where one could be added
- CSS using `left/right` instead of logical properties
- Concatenated strings that work but aren't ideal for translators

### 4. Apply Context

Not everything needs fixing. Use judgment:

**Probably needs attention:**
- User-facing dates without locale formatting
- Forms with required State/ZIP fields
- Fixed-width containers with text
- Hardcoded currency symbols users will see

**Probably fine:**
- Internal logging timestamps
- Developer-facing debug output
- Config files with technical strings
- Third-party library code you don't control

## Reference

For detailed patterns to check, see `references/i18n-checklist.md`. Use this as a guide for what to look for, not a checklist to grep through.

## Output Format

Keep it **compact**. Group by severity, use tables, actionable fixes.

```markdown
## i18n Analysis: [path]

[1-2 sentences: What is this? i18n setup present? Overall readiness?]

**Readiness:** Not ready / Partial / Good / Excellent

---

### Critical (breaks functionality)

| Location | Issue | Who's Affected | Fix |
|----------|-------|----------------|-----|
| form.tsx:17 | Hardcoded MM/DD/YYYY | Non-US users (ambiguous date) | `Intl.DateTimeFormat(locale)` |
| form.tsx:52 | Required "State" field | International users | Make optional or use "Region" |

### Serious (degraded experience)

| Location | Issue | Who's Affected | Fix |
|----------|-------|----------------|-----|
| card.tsx:34 | Fixed 200px width | German (+30% text) | Use flexible width |
| btn.tsx:72 | `text-align: left` | RTL users (Arabic, Hebrew) | `text-align: start` |

### Minor (improvements)

| Location | Issue | Fix |
|----------|-------|-----|
| utils.ts:15 | Hardcoded `$` | `Intl.NumberFormat` |

---

### Exceptions

- Timestamp in logger.ts:8 — internal debug, fine

### Summary

**5 issues**: 2 critical, 2 serious, 1 minor. Priority: date format and State field block international users.

**i18n setup:** None detected. Consider react-intl or i18next.
```

## Output Guidelines

- **Use tables** grouped by severity—Critical/Serious/Minor
- **"Who's Affected" column**—makes impact concrete
- **Fix column**—specific solution, not generic advice
- **Readiness rating upfront**—quick assessment
- **Summary as TL;DR**—counts, priority, i18n tooling status

## What Makes This Different From a Linter

A linter would flag every `margin-left`. You should:

1. **Understand the UI** - Is this actually directional or just spacing?
2. **Assess real impact** - Will this actually break for RTL users?
3. **Prioritize by visibility** - User-facing > internal tooling
4. **Consider the stack** - Does this project even need RTL support?

Your value is understanding **user impact**, not finding patterns.

Files: 1

Size: 5.2 KB

Complexity: 13/100

Category: Design

Source: https://github.com/hereinthehive/gotrino-inclusion/tree/main/skills/i18n-check

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts