symfony-sk:label

Propose and validate translation labels before writing them to migrations.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Swoking/symfony-sk-plugin --skill symfony-sk-label
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symfony-sk:label
Source: https://github.com/Swoking/symfony-sk-plugin/tree/main/plugins/symfony-sk/skills/label
Command: npx skills add https://github.com/Swoking/symfony-sk-plugin --skill symfony-sk-label

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add translation labels to migrations so that all UI text across the application can be localized and managed consistently.

Core Features & Use Cases

  • Determine the key name, target (fo/bo), and translations.
  • Validate via AskUserQuestion before writing to migrations, ensuring human confirmation.
  • Apply translations to migrations and support common UI elements like titles, buttons, messages, and placeholders.
  • Example usage: Create a label with FR/EN translations and apply via the migration pipeline.

Quick Start

Provide a label key, target, and translations, then approve the suggested changes to write to migrations.

Frequently Asked Questions about symfony-sk:label

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

FAQPage Schema
How do I add i18n translation labels to Symfony migrations?

To add i18n translation labels to Symfony migrations, you provide a label key, target, and translations. The Skill proposes and validates these labels before writing them to the migration pipeline for UI text localization.

What is the best way to manage UI text localization in Symfony migrations?

Managing UI text localization in Symfony migrations involves attaching translation labels to all UI contexts like titles, buttons, and messages. This ensures consistent application-wide text management through the migration pipeline.

Can I validate Symfony translation keys before applying them to migrations?

Yes, you validate Symfony translation keys before applying them to migrations. The Skill performs naming convention and language checks, then requires explicit user confirmation via AskUserQuestion before persisting any label changes.

How do I apply translations to different UI elements using Symfony migrations?

You apply translations to different UI elements by proposing labels that target specific contexts. The Skill supports applying localized text to titles, buttons, messages, and placeholders directly within the Symfony migration structure.

Does this approach support both front-end and back-end translation targets?

Yes, this approach supports both front-end and back-end translation targets. When defining a translation label, you specify the target as either front-office or back-office, ensuring the localized UI text applies to the correct application context.