ofcskn

Automatically internationalize React components in the minimalblock app for Turkish (tr) and English (en). Detects static text, generates keys, adds translations to both locale files, and replaces hardcoded strings with t() calls. No static text allowed — only i18n.

Write and maintain unit tests for React components (libs/ui), feature hooks (libs/features), domain logic (libs/core), and AI prompt builders (libs/ai). Covers rendering, interaction, performance guards, and input validation. Use after every UI, hook, or domain change.

Expert in Google Gemini multimodal API integration for the 3D generative media app. Handles prompt engineering, image-to-3D conversion pipelines, token budgeting, error handling, and response parsing in libs/ai.

Manage and extend the Nx workspace for the 3D media app. Use for adding libs, configuring targets, fixing project graph issues, adjusting tsconfig paths, and running tasks correctly.

Audit and optimise frontend performance for the 3D media app. Covers Vite bundle analysis, 3D asset loading, route code-splitting, image optimisation, and Supabase query performance. Use for slow pages, heavy bundles, or poor loading experience.

Strategic authority for the 3D Generative Media App. Translates ambiguous requests into scoped product decisions, milestone cuts, acceptance criteria, and implementation priorities aligned with the 2-day sprint constraint.

Design and implement Supabase schema, migrations, Storage configuration, and typed client usage for the 3D media app. Use for new tables, views, RPC functions, storage buckets, and migration authoring.

Review and harden Supabase RLS policies, storage access policies, auth configuration, SQL function privileges, and schema exposure for the 3D media app. Use for any auth-sensitive migration, policy design, or security audit.

Automates the full mobile app release pipeline — version management, localized metadata, multi-device screenshot generation, i18n translations, and store submission for iOS and Android. Use when the user asks to "release my app", "bump the version", "generate store screenshots", "update metadata in all languages", "prepare a store submission", "sync translations", or "manage my app versions across platforms". Orchestrates sub-skills: managing-app-versions, generating-store-screenshots, managing-store-metadata, managing-app-localizations, submitting-app-release.

Manages the two-phase store screenshot pipeline: Phase 1 captures raw screenshots by automatically exploring the running iOS Simulator or Android Emulator — booting the device, launching the app, navigating every key screen, and capturing numbered PNGs; Phase 2 adds design layers (device frames, headlines, backgrounds) exclusively via ParthJadhav/app-store-screenshots (MIT). Outputs are grouped by locale/platform/device-size so folders can be downloaded and uploaded directly. Use when the user says "generate screenshots", "update store images", "take screenshots", "design marketing slides", or "screenshot pipeline".

Manages i18n translation files and store metadata localization across iOS, Android, and Google Play. Use when the user says "add a language", "fix missing translations", "translate strings", "audit i18n", "missing locale keys", or any task involving language support. Source of truth for translation keys is .msd/locales/{app-id}/en.json.

Validates iOS and Android app permissions — checks that all iOS NSUsageDescription strings are present and non-empty, detects dangerous or deprecated Android permissions, and cross-references declared permissions with actual API usage in the codebase. Use before every store submission to avoid rejection. Use /msd-permissions to run interactively.

Manages the registry of known apps in .msd/memory/apps.json. Use when initializing a new app, updating app state (first release complete, new locale added), discovering apps in a directory, or reading current app status. Always read the registry before any release operation to check if first-release setup is complete.

Manages semantic versioning for mobile apps across iOS and Android platforms. Use when the user says "bump version", "increment build number", "set version to", "release patch/minor/major", or "sync build numbers". Single source of truth is .msd/versions/{app-id}/version.json. Syncs to app.json (Expo), Info.plist (native iOS), and build.gradle (native Android).

Manages App Store Connect and Google Play Console metadata — names, subtitles, keywords, descriptions, and release notes — enforcing Apple and Google hard character limits. Use when the user says "update description", "change keywords", "edit metadata", "update release notes", or "validate store copy". Always run validate-metadata.js after any edit before uploading.

Optimizes App Store Optimization (ASO) strategy across all metadata fields for both Apple App Store and Google Play. Covers keyword research, competitor gap analysis, character-limit-aware copy, and screenshot caption alignment with Apple OCR indexing. Use when the user says "optimize keywords", "improve ASO", "keyword research", "improve ranking", or "write metadata". Use lenses/aso-optimizer.lens.md for AI-powered metadata generation per locale.