laravel-raptor-i18n

Scan Laravel projects for hardcoded English strings and generate i18n reports.

Updated Mar 19, 2026

Search Tags:#vue #localization #translation #laravel #code-quality #i18n #blade

Ready to run

npx skills add https://github.com/callcocam/raptor-skils --skill laravel-raptor-i18n

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel-raptor-i18n
Source: https://github.com/callcocam/raptor-skils/tree/main/laravel-raptor-i18n
Command: npx skills add https://github.com/callcocam/raptor-skils --skill laravel-raptor-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams locate and fix hardcoded English strings across a Laravel project, ensuring translations exist in pt_BR/lang before applying changes with a controlled workflow.

Core Features & Use Cases

Discover hardcoded texts in Vue templates, Blade templates, and PHP components (controllers, services, enums) across app and packages.
Generate a comprehensive i18n report by file, including suggested translation keys and where to create them.
Apply per-file corrections only after user confirmation, with verification that keys exist in lang/pt_BR and proper fallbacks.

Quick Start

Run a full i18n scan of the Laravel project to identify hardcoded English strings and prepare a translation plan.

Frequently Asked Questions about laravel-raptor-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find hardcoded English strings in a Laravel project?▼

To find hardcoded English strings in a Laravel project, scan Vue templates, Blade files, and PHP components to generate a comprehensive report identifying untranslated texts and suggesting appropriate translation keys.

What is the best way to replace hardcoded text with translation keys in Blade and Vue templates?▼

The best way to replace hardcoded text with translation keys is using a controlled workflow that enforces Laravel i18n conventions for Blade and Vue, applying per-file corrections only after verifying keys exist in your language files.

Does this i18n scanning workflow support PHP controllers and enums?▼

Yes, this i18n scanning workflow supports PHP controllers, services, and enums. It discovers hardcoded texts across your app and packages, enforcing Laravel i18n conventions for all PHP components before applying any changes.

Can I automatically fix Laravel translation keys without manual confirmation?▼

No, you cannot automatically fix Laravel translation keys without manual confirmation. The workflow applies per-file corrections only after user confirmation and verifies keys exist in the lang/pt_BR directory before making changes.

Why does my Laravel translation workflow require checking the lang/pt_BR directory?▼

Checking the lang/pt_BR directory is required to ensure proper fallbacks exist before applying changes. This guarantees suggested translation keys are verified against your existing language structure, preventing missing translations.