تشغيل أي مهارة في Manus بنقرة واحدة

translations

النجوم٠

التفرعات٠

آخر تحديث٢٠ مايو ٢٠٢٦ في ٢١:٤٥

Rules for internationalization in flutter_starter — never hardcode user-facing strings, use LocaleKeys.x.tr(context) with optional args for placeholders, add new keys to assets/translations/translations.json (numbered for shared, named for feature-specific), run the codegen helper, and never edit generated locale files. Covers pluralization via _zero/_one/_two/_few/_many/_other suffixes. Use when adding any user-visible text, validation messages, snackbar content, or dialog content.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

aymansalkhatib

aymansalkhatib/flutter-starter

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

SKILL.md

readonly

name

translations

description

Translations

Every string shown to the user flows through translations. Never write English/Arabic literals in Text, hints, labels, validators, error messages, snackbars, or dialogs.

// ✅
Text(LocaleKeys.welcome.tr(context))

// ✅ with placeholder args
Text(LocaleKeys.greetName.tr(context, args: {'name': user.name}))

// ❌
Text('Welcome')
Text('مرحبا')

Placeholders use {{name}} syntax and are replaced via args.

Workflow when a new string is needed

Open assets/translations/translations.json — read the last ~30 lines to find the last key.
Add a new entry:
- Shared / common string → use the next integer key: "88": { "en": "...", "ar": "..." } The Dart identifier is auto-derived from the English text (camelCase).
- Feature-specific string → use a named string key: "productsTitle": { "en": "...", "ar": "..." } The key name becomes the Dart identifier directly (first letter lowercased).
Run dart helpers/translation_codegen.dart — regenerates en.json, ar.json, and lib/generated/locale_keys.dart.
Use LocaleKeys.<key>.tr(context) in widget code.

Never edit assets/locales/en.json, assets/locales/ar.json, or lib/generated/locale_keys.dart directly — they are overwritten on every codegen run.

Runtime locale switching

Use TranslationManager (core/localization/translation_manager.dart) — it persists the choice and rebuilds the app. Never call Localizations.localeOf for switching.

Pluralization

Arabic has six plural forms (zero, one, two, few, many, other). Never implement with ternaries in widget code — use the plural-key convention:

// en.json
"itemCount_zero":  "No items",
"itemCount_one":   "{{count}} item",
"itemCount_other": "{{count}} items"

// ar.json
"itemCount_zero":  "لا عناصر",
"itemCount_one":   "عنصر واحد",
"itemCount_two":   "عنصران",
"itemCount_few":   "{{count}} عناصر",
"itemCount_many":  "{{count}} عنصرًا",
"itemCount_other": "{{count}} عنصر"

Consume via LocaleKeys.itemCount.plural(context, count: items.length).

المزيد من هذا المستودع

نفس المستودع

architecture

aymansalkhatib/flutter-starter

Clean Architecture layer rules, feature folder structure, import direction, and no-backend feature scaffolding for flutter_starter. Use when deciding where a new file belongs, reviewing dependency direction between domain/data/presentation, structuring a feature folder, or building a presentation-only feature (splash, onboarding, info).

2026-05-200

code-style

aymansalkhatib/flutter-starter

Code style rules and anti-patterns for flutter_starter — comment discipline (write only for non-obvious why), SOLID principles, no speculative abstractions, and a concrete anti-patterns table covering dartz vs custom Either, datasource-returns-Either, e.toString() in Failure, emit vs safeEmit, state.navigateToX, Navigator.of(context).push* directly, raw-map route args, hardcoded Colors.white / TextStyle / EdgeInsets, print / AppLogger.debug, @freezed class (non-abstract), TextEditingController in StatefulWidget, AppBar in body widget, setState inside BlocConsumer. Use before finalizing any Dart file in this project.

2026-05-200

data-layer

aymansalkhatib/flutter-starter

Rules for the data layer in flutter_starter — RemoteDataSource using ApiClient, RepositoryImpl as the Either boundary with exception-to-Failure mapping, cache-first read patterns, Dio timeouts, and the Failure error-code ranges. Use when creating or editing any file under lib/features/*/data/, or when mapping exceptions to Failure.

2026-05-200

di-registration

aymansalkhatib/flutter-starter

Rules for dependency injection with GetIt (sl) in flutter_starter — every feature owns a di/<feature>_dependencies.dart registered in service_locator.dart, with registration order DataSources → Repository → UseCases → Cubit, and lazy-singleton vs factory guidance. Use when creating a new feature's DI file, editing service_locator.dart, or deciding how to register a service.

2026-05-200

domain-layer

aymansalkhatib/flutter-starter

Rules for the domain layer in flutter_starter — Freezed entities with self-owned fromJson, UseCase + Params pattern, and abstract Repository contracts. Use when creating or editing any file under lib/features/*/domain/, or deciding whether a feature needs a separate Model class beyond its Entity.

2026-05-200

generate-feature

aymansalkhatib/flutter-starter

Orchestrator for scaffolding a new Flutter Clean Architecture feature end-to-end in flutter_starter — enforces mode selection (quick / detailed), the intake ritual, the strict generation order across layers, and the feature-delivery checklist. Supports two modes — quick (5 basic questions) and detailed (expanded API contracts with exact request / response shapes). Delegates detailed rules to the per-layer skills (architecture / domain-layer / data-layer / presentation-layer / hive-caching / security / di-registration / navigation / translations). Use when the user asks to create a new feature with domain, data, and presentation layers.

2026-05-200

name

translations

description

Translations

Every string shown to the user flows through translations. Never write English/Arabic literals in Text, hints, labels, validators, error messages, snackbars, or dialogs.

// ✅
Text(LocaleKeys.welcome.tr(context))

// ✅ with placeholder args
Text(LocaleKeys.greetName.tr(context, args: {'name': user.name}))

// ❌
Text('Welcome')
Text('مرحبا')

Placeholders use {{name}} syntax and are replaced via args.

Workflow when a new string is needed

Open assets/translations/translations.json — read the last ~30 lines to find the last key.
Add a new entry:
- Shared / common string → use the next integer key: "88": { "en": "...", "ar": "..." } The Dart identifier is auto-derived from the English text (camelCase).
- Feature-specific string → use a named string key: "productsTitle": { "en": "...", "ar": "..." } The key name becomes the Dart identifier directly (first letter lowercased).
Run dart helpers/translation_codegen.dart — regenerates en.json, ar.json, and lib/generated/locale_keys.dart.
Use LocaleKeys.<key>.tr(context) in widget code.

Never edit assets/locales/en.json, assets/locales/ar.json, or lib/generated/locale_keys.dart directly — they are overwritten on every codegen run.

Runtime locale switching

Use TranslationManager (core/localization/translation_manager.dart) — it persists the choice and rebuilds the app. Never call Localizations.localeOf for switching.

Pluralization

Arabic has six plural forms (zero, one, two, few, many, other). Never implement with ternaries in widget code — use the plural-key convention:

// en.json
"itemCount_zero":  "No items",
"itemCount_one":   "{{count}} item",
"itemCount_other": "{{count}} items"

// ar.json
"itemCount_zero":  "لا عناصر",
"itemCount_one":   "عنصر واحد",
"itemCount_two":   "عنصران",
"itemCount_few":   "{{count}} عناصر",
"itemCount_many":  "{{count}} عنصرًا",
"itemCount_other": "{{count}} عنصر"

Consume via LocaleKeys.itemCount.plural(context, count: items.length).