Cursor rule

1---
2description: Locales coding standards and best practices guide
3globs: locales/*.json
4alwaysApply: false
5---
6# Translation Development Standards
7 
8Auto-attached when working in `locales/` directory.
9 
10## File Structure
11 
12```
13locales/
14├── en.default.json     # English (required)
15├── es.json             # Spanish
16├── fr.json             # French
17└── de.json             # German
18```
19 
20## Key Organization
21 
22**Hierarchical Structure:**
23```json
24{
25  "general": {
26    "meta": {
27      "title": "{{ shop_name }}",
28      "description": "{{ shop_description }}"
29    },
30    "accessibility": {
31      "skip_to_content": "Skip to content",
32      "close": "Close"
33    }
34  },
35  "products": {
36    "add_to_cart": "Add to cart",
37    "quick_view": "Quick view",
38    "price": {
39      "regular": "Regular price",
40      "sale": "Sale price",
41      "unit": "Unit price"
42    }
43  }
44}
45```
46**Usage**
47```liquid
48{{ 'general.meta.title' | t: shop_name: shop.name }}
49{{ 'general.meta.description' | t: shop_description: shop.description }}
50```
51 
52## Translation Guidelines
53 
54**Key Naming:**
55- Use descriptive, hierarchical keys
56- Maximum 3 levels deep
57- Use snake_case for key names
58- Group related translations
59 
60**Content Rules:**
61- Keep text concise for UI elements
62- Use variables for dynamic content
63- Consider character limits
64- Maintain consistent terminology
65 
66**Schema Translations:**
67 
68Use the rules outlined in our [typescript schema](schemas/schema.d.ts) to determine the appropriate key structure for schema translations.
69