@jjlmoya/utils-performing-arts 1.1.0

package/prompts/i18n/ko.md

@@ -0,0 +1,16 @@
+# Prompts-어 (ko)
+
+## 번역
+
+다음 내용을 한국어로 현지화하세요.
+
+번역하지 말고, 현지화하세요. 목표는 단어를 한 언어에서 다른 언어로 옮기는 것이 아니라, 실제 사람이 처음부터 한국어로 직접 쓴 것처럼 읽히는 텍스트를 만드는 것입니다. 잘 현지화된 텍스트에는 원본 언어의 흔적이 남지 않습니다.
+
+인간의 목소리로 쓰세요: 친근하고, 명확하며, 전문적으로. 기계적인 표현, 어색한 문장 구조, 사용 설명서처럼 들리는 표현은 피하세요. 한국어로 자연스럽게 읽히지 않는 부분이 있다면, 자연스러워질 때까지 다시 표현하세요.
+
+준수해야 할 지침:
+
+- 표현, 비유, 문화적 참조를 한국어 사용 환경에서 자연스럽게 공감될 수 있도록 조정하세요.
+- 기술 용어는 한국어권에서 가장 널리 통용되는 형태로 유지하고, 명확한 대응어가 없으면 원문 용어를 그대로 사용하세요.
+- 원본의 형식(마크다운, 목록, 제목)을 유지하세요.
+- 원문에서 정보를 추가하거나 생략하지 마세요.

package/prompts/i18n/nl.md

@@ -0,0 +1,16 @@
+# Prompts-derlands (nl)
+
+## Vertaling
+
+Lokaliseer de volgende inhoud naar het Nederlands.
+
+Vertaal niet: lokaliseer. Het doel is niet om woorden van de ene taal naar de andere over te zetten, maar om een tekst te produceren die klinkt alsof hij vanaf het begin door een echte persoon in het Nederlands is geschreven. Een goed gelokaliseerde tekst laat geen spoor van de brontaal achter.
+
+Schrijf met een menselijke stem: warm, helder en professioneel. Vermijd machinale zinnen, geforceerde constructies en alles wat klinkt als een handleiding. Als iets niet natuurlijk stroomt in het Nederlands, herschrijf het dan totdat het dat wel doet.
+
+Richtlijnen om te volgen:
+
+- Pas uitdrukkingen, metaforen en culturele verwijzingen aan zodat ze natuurlijk resoneren in een Nederlandstalige context.
+- Gebruik technische termen in hun meest gangbare vorm in de Nederlandstalige wereld; als er geen duidelijk equivalent bestaat, behoud dan de originele term.
+- Respecteer de opmaak van het origineel (markdown, lijsten, koppen).
+- Voeg geen informatie toe en laat geen informatie weg ten opzichte van het origineel.

package/prompts/i18n/pl.md

@@ -0,0 +1,16 @@
+# Prompts-lski (pl)
+
+## Tłumaczenie
+
+Zlokalizuj poniższą treść na język polski.
+
+Nie tłumacz-kalizuj. Celem nie jest przeniesienie słów z jednego języka do drugiego, lecz stworzenie tekstu, który brzmi tak, jakby od początku napisała go prawdziwa osoba po polsku. Dobrze zlokalizowany tekst nie zdradza języka źródłowego.
+
+Pisz ludzkim głosem: bliskim, jasnym i profesjonalnym. Unikaj maszynowego języka, wymuszonych zwrotów i zdań brzmiących jak instrukcja obsługi. Jeśli coś nie brzmi naturalnie po polsku, przeredaguj to tak, żeby brzmiało.
+
+Wytyczne do przestrzegania:
+
+- Dostosuj wyrażenia, metafory i odniesienia kulturowe do tego, co naturalnie rezonuje w polskojęzycznym kontekście.
+- Zachowaj terminy techniczne w ich najbardziej rozpoznawalnej formie w polskim środowisku; jeśli nie istnieje wyraźny odpowiednik, zachowaj oryginalny termin.
+- Zachowaj formatowanie oryginału (markdown, listy, nagłówki).
+- Nie dodawaj ani nie pomijaj żadnych informacji z oryginału.

package/prompts/i18n/pt.md

@@ -0,0 +1,16 @@
+# Prompts-rtuguês (pt)
+
+## Tradução
+
+Localize o seguinte conteúdo para o português.
+
+Não traduza: localize. O objetivo não é transferir palavras de um idioma para outro, mas produzir um texto que pareça ter sido escrito originalmente em português por uma pessoa real. Um texto bem localizado não traz nenhum rastro do idioma de origem.
+
+Escreva com voz humana: próxima, clara e profissional. Evite linguagem de máquina, construções forçadas e frases que soam como manual técnico. Se algo não fluir de forma natural em português, reformule até que flua.
+
+Critérios a respeitar:
+
+- Adapte expressões, metáforas e referências culturais ao que ressoaria de forma natural num contexto lusófono.
+- Mantenha os termos técnicos na forma mais reconhecida no mundo lusófono; se não existir um equivalente claro, conserve o termo original.
+- Respeite a formatação do original (markdown, listas, cabeçalhos).
+- Não acrescente nem omita informação em relação ao original.

package/prompts/i18n/ru.md

@@ -0,0 +1,16 @@
+# Prompts-сский (ru)
+
+## Перевод
+
+Локализуйте следующий контент на русский язык.
+
+Не переводите-кализуйте. Цель не в том, чтобы перенести слова из одного языка в другой, а в том, чтобы создать текст, который звучит так, словно его с самого начала написал живой человек по-русски. В хорошо локализованном тексте не остаётся следов языка оригинала.
+
+Пишите человеческим голосом: тёплым, ясным и профессиональным. Избегайте машинного языка, вынужденных конструкций и фраз, которые звучат как инструкция по эксплуатации. Если что-то не звучит по-русски естественно, перефразируйте это так, чтобы звучало.
+
+Принципы, которых следует придерживаться:
+
+- Адаптируйте выражения, метафоры и культурные отсылки к тому, что естественно воспринимается в русскоязычном контексте.
+- Используйте технические термины в их наиболее распространённой форме в русскоязычном мире; если чёткого эквивалента нет, сохраните оригинальный термин.
+- Соблюдайте форматирование оригинала (markdown, списки, заголовки).
+- Не добавляйте и не опускайте никакой информации по сравнению с оригиналом.

package/prompts/i18n/sv.md

@@ -0,0 +1,16 @@
+# Prompts-enska (sv)
+
+## Översättning
+
+Lokalisera följande innehåll till svenska.
+
+Översätt inte: lokalisera. Målet är inte att överföra ord från ett språk till ett annat, utan att producera en text som låter som om den skrevs direkt på svenska av en verklig person. En välokaliserad text lämnar inga spår av källspråket.
+
+Skriv med en mänsklig röst: varm, tydlig och professionell. Undvik maskinspråk, krystade konstruktioner och meningar som låter som en instruktionsmanual. Om något inte flödar naturligt på svenska, skriv om det tills det gör det.
+
+Riktlinjer att följa:
+
+- Anpassa uttryck, metaforer och kulturella referenser till vad som skulle resonera naturligt i ett svenskspråkigt sammanhang.
+- Använd tekniska termer i deras mest vedertagna form i den svenskspråkiga världen; om det inte finns något tydligt motsvarande, behåll den ursprungliga termen.
+- Respektera originalets formatering (markdown, listor, rubriker).
+- Lägg inte till eller utelämna någon information jämfört med originalet.

package/prompts/i18n/tr.md

@@ -0,0 +1,16 @@
+# Prompts-rkçe (tr)
+
+## Çeviri
+
+Aşağıdaki içeriği Türkçeye yerelleştirin.
+
+Çeviri yapmayın: yerelleştirin. Amaç, kelimeleri bir dilden diğerine aktarmak değil; sanki başından beri gerçek bir kişi tarafından Türkçe yazılmış gibi okunan bir metin üretmektir. İyi yerelleştirilmiş bir metinde kaynak dilin izi kalmaz.
+
+İnsan sesiyle yazın: sıcak, açık ve profesyonel. Makine diline, zoraki ifadelere ve kullanım kılavuzu gibi ses çıkaran cümlelere yer vermeyin. Türkçede doğal akmayan bir şey varsa, akana kadar yeniden ifade edin.
+
+Uyulması gereken yönergeler:
+
+- İfadeleri, metaforları ve kültürel referansları Türkçe konuşan bir bağlamda doğal yankı uyandıracak şekilde uyarlayın.
+- Teknik terimleri Türkçe konuşan dünyada en yaygın bilinen biçimleriyle kullanın; net bir karşılık yoksa orijinal terimi koruyun.
+- Orijinalin biçimlendirmesine (markdown, listeler, başlıklar) uyun.
+- Orijinale göre bilgi eklemeyin veya çıkarmayın.

package/prompts/i18n/zh.md

@@ -0,0 +1,16 @@
+# Prompts- (zh)
+
+## 翻译
+
+请将以下内容本地化为中文。
+
+不要翻译，要本地化。目标不是将词语从一种语言转移到另一种语言，而是产出一段读起来像是由真实的人直接用中文写成的文字。本地化质量上乘的文本不会留下任何源语言的痕迹。
+
+以人的声音书写：亲切、清晰、专业。避免机器腔、生硬的表达方式，以及任何听起来像操作手册的句子。如果某些内容用中文读起来不自然，就重新表达，直到自然为止。
+
+请遵循以下准则：
+
+- 将表达方式、比喻和文化参照调整为在中文语境中能够自然共鸣的内容。
+- 技术术语请使用在中文世界最广为人知的形式；如果没有明确的对应词，保留原文术语。
+- 保留原文的格式（markdown、列表、标题）。
+- 不得增加或删减原文中的任何信息。

package/prompts/seo.md

@@ -0,0 +1,58 @@
+Aquí tienes la Mega-Prompt Final Evolucionada. Está diseñada para que sea un estándar universal: funciona para calculadoras, conversores, generadores o cualquier utilidad técnica.
+
+El secreto de esta prompt es que no pide "un texto", sino una arquitectura de información que Google interpreta como contenido de alta calidad (E-E-A-T).
+
+La Prompt: El Arquitecto de Utilidades SEO
+Copia y pega lo siguiente:
+
+Actúa como un Especialista SEO Senior experto en Programmatic SEO y Herramientas Online para el sector veterinario y de mascotas. Tu misión es redactar el contenido de apoyo para una página cuya función principal es una utilidad interactiva (calculadora, conversor o generador).
+
+Objetivo: Crear un texto semántico de entre 400 y 600 palabras que aporte autoridad y contexto técnico sin distraer al usuario de la herramienta principal.
+
+Tu "Caja de Herramientas" de componentes Astro:
+
+SEOArticle: Contenedor raíz.
+
+SEOTitle: Encabezados (level 2 para secciones, level 3 para subsecciones).
+
+SEOList: Pasos de uso o beneficios.
+
+SEOTable: Datos de referencia, rangos o comparativas.
+
+SEOTip: El "Consejo del experto" (ideal para recomendaciones veterinarias).
+
+SEOCard: Resaltar conceptos clave o fórmulas (ej: fórmula RER, etapas de vida).
+
+SEOStats: Datos numéricos o estadísticas del sector (ej: % de mascotas con sobrepeso).
+
+SEOGlossary: Definiciones técnicas rápidas (RER, DER, kcal/kg, etc.).
+
+SEOProsCons: Ventajas y limitaciones de la herramienta.
+
+SEOSummary: Resumen ejecutivo (TL;DR) para situar justo debajo del título.
+
+SEODiagnostic: Checklist de validación o "Cuándo usar esta herramienta".
+
+Reglas de Oro:
+
+Prioriza la Escaneabilidad: El usuario quiere respuestas rápidas. Usa frases cortas y muchos componentes visuales.
+
+Contexto Semántico: Incluye palabras clave LSI (latentes) y responde a la intención de búsqueda secundaria (el "qué pasa después" de usar la herramienta).
+
+Autoridad Veterinaria: Cita fuentes reales (WSAVA, FEDIAF, AAHA) cuando sea relevante. El tono debe ser de experto en nutrición o medicina animal, no genérico.
+
+Estructura Obligatoria:
+
+Un <SEOSummary> al inicio con los puntos clave.
+
+Una sección de "Cómo funciona" usando <SEOList> o <SEOCard>.
+
+Una <SEOTable> con datos de referencia (ej: factores RER/DER, equivalencias de edad, valores calóricos).
+
+Un <SEOTip> con valor añadido real (consejo del veterinario).
+
+Un <SEODiagnostic> para ayudar al usuario a interpretar sus resultados.
+
+Formato de Salida:
+Devuelve exclusivamente el código para un archivo .astro. No incluyas explicaciones innecesarias fuera del código. Usa las props correctamente (ej: <SEOTitle level={2}>).
+

package/prompts/translations/french.md

@@ -0,0 +1,33 @@
+# Guide de Traduction Technique Élite (Français)
+
+Tu es un expert natif français, spécialiste en médecine vétérinaire et passionné de bien-être animal. Ton objectif est de traduire les utilitaires de @jjlmoya/utils-pets avec une précision chirurgicale tout en dominant les résultats de recherche (SEO long-tail).
+
+## Ta Mission
+Transformer un fichier technique TypeScript (EN/ES) en une version française qui semble avoir été écrite par un vétérinaire praticien né en France. Pas de traduction littérale, mais une adaptation naturelle et fluide du domaine vétérinaire.
+
+## Principes de Fer (Règles Strictes)
+- **ZÉRO Commentaires**: Aucun commentaire dans le code (`//` ou `/* */`). Ton code doit être pur.
+- **Intégrité TypeScript**: Préserve exactement la structure des objets et les types (ex: `PetAgeLocaleContent`, `PetRationLocaleContent`, imports, etc.).
+- **SEO Long-Tail Dominant**: Les slugs doivent être riches en mots-clés stratégiques pour le marché français.
+  - Âge: `calculateur-age-chien-chat-annees-humaines`
+  - Ration: `calculateur-ration-quotidienne-chien-chat-nutrition`
+- **Langage Naturel & Expert**: Utilise le "Vous" (formel). Emploie des termes techniques premium : *RER*, *DER*, *ration journalière*, *stade de vie*, *besoins énergétiques*, *condition corporelle*, *métabolisme basal*.
+
+## Vocabulaire Vétérinaire de Référence
+- RER (Resting Energy Requirement) → Besoins Énergétiques au Repos (BER)
+- DER (Daily Energy Requirement) → Besoins Énergétiques Journaliers (BEJ)
+- Life stage → Stade de vie
+- Puppy / Kitten → Chiot / Chaton
+- Senior → Senior (ou Âgé)
+- Sterilised → Stérilisé(e)
+- Dry food → Croquettes / Aliment sec
+- Wet food → Pâtée / Aliment humide
+- Body weight → Poids corporel
+- Caloric density → Densité calorique (kcal/kg)
+
+## Structure de la SEO
+Dans la section `seo`, assure-toi que le contenu est riche (400-600 mots), structuré avec des balises HTML (`<strong>`, `<h3>`) et des listes qui apportent une réelle valeur ajoutée au propriétaire d'animal. Cite des sources reconnues : WSAVA, FEDIAF, AAHA.
+
+## Fichier Source à Traduire
+[Colle ici le contenu source]
+

package/scripts/postinstall.mjs

@@ -0,0 +1,27 @@
+import { readFileSync, writeFileSync, mkdirSync, readdirSync } from 'fs';
+import { join, dirname } from 'path';
+import { fileURLToPath } from 'url';
+
+const libDir = dirname(fileURLToPath(import.meta.url));
+const toolsDir = join(libDir, '../src/tool');
+
+const inNodeModules = libDir.includes('node_modules');
+if (!inNodeModules) process.exit(0);
+
+const projectRoot = join(libDir, '../../../..');
+const categoryKey = JSON.parse(readFileSync(join(libDir, '../package.json'), 'utf8')).name.replace('@jjlmoya/utils-', '');
+const destDir = join(projectRoot, `public/styles/lib/${categoryKey}`);
+
+mkdirSync(destDir, { recursive: true });
+
+const tools = readdirSync(toolsDir, { withFileTypes: true }).filter(d => d.isDirectory());
+for (const tool of tools) {
+    const toolDir = join(toolsDir, tool.name);
+    let files;
+    try { files = readdirSync(toolDir).filter(f => f.endsWith('.css')); }
+    catch { continue; }
+    for (const file of files) {
+        writeFileSync(join(destDir, file), readFileSync(join(toolDir, file)));
+        console.log(`[@jjlmoya/utils-${categoryKey}] copied ${file}`);
+    }
+}

package/src/category/PerformingArtsCategorySEO.astro

@@ -0,0 +1,9 @@
+---
+import { SEORenderer } from '@jjlmoya/utils-shared';
+import { performingArtsCategory } from './index';
+
+const locale: string = Astro.props.locale ?? 'es';
+const categoryContent = await performingArtsCategory.i18n[locale as keyof typeof performingArtsCategory.i18n]?.();
+---
+
+{categoryContent && <SEORenderer content={{ locale, sections: categoryContent.seo }} />}

package/src/category/i18n/de.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Werkzeuge für Probenplanung in der darstellenden Kunst';
+const description = 'Lokale Browser-Werkzeuge für Probenplanung, Besetzungslisten, Verfügbarkeitskonflikte und übersichtliche Produktionstage.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/en.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Performing Arts Rehearsal Tools';
+const description = 'Private browser tools for planning rehearsals, building call sheets, spotting availability conflicts, and keeping a production day readable.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/es.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Herramientas de ensayo para artes escénicas';
+const description = 'Herramientas privadas en el navegador para planificar ensayos, crear convocatorias, detectar conflictos y ordenar cada jornada de producción.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/fr.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Outils de répétition pour les arts du spectacle';
+const description = 'Outils privés dans le navigateur pour planifier les répétitions, préparer les convocations, repérer les conflits et organiser la production.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/id.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Alat latihan seni pertunjukan';
+const description = 'Alat privat di browser untuk merencanakan latihan, membuat lembar panggilan, menemukan konflik ketersediaan, dan menata hari produksi.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/it.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Strumenti per le prove delle arti performative';
+const description = 'Strumenti privati nel browser per pianificare le prove, creare i fogli di convocazione, trovare conflitti e organizzare la giornata.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/ja.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = '舞台芸術のリハーサルツール';
+const description = 'リハーサル計画、出演者の連絡表、空き時間の確認、制作日の整理に使えるブラウザ上のプライベートツールです。';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/ko.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = '공연 예술 리허설 도구';
+const description = '리허설 계획, 콜시트 작성, 일정 충돌 확인, 제작일 정리를 돕는 브라우저 기반 비공개 도구입니다.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/nl.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Repetitietools voor podiumkunsten';
+const description = 'Privétools in de browser voor repetitieplanning, callsheets, beschikbaarheidsconflicten en een overzichtelijke productiedag.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/pl.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Narzędzia prób dla sztuk scenicznych';
+const description = 'Prywatne narzędzia w przeglądarce do planowania prób, kart obsady, wykrywania konfliktów i porządkowania dnia produkcji.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};

package/src/category/i18n/pt.ts

@@ -0,0 +1,27 @@
+import type { CategoryLocaleContent } from '../../types';
+
+const slug = 'performing-arts';
+const title = 'Ferramentas de ensaio para artes performativas';
+const description = 'Ferramentas privadas no navegador para planear ensaios, criar folhas de chamada, detetar conflitos e organizar o dia de produção.';
+
+export const content: CategoryLocaleContent = {
+  slug,
+  title,
+  description,
+  seo: [
+    { type: 'title', text: 'Build a Rehearsal Day from Real Constraints', level: 2 },
+    { type: 'paragraph', html: 'A rehearsal plan has to hold several truths at once: scenes need time, people need to be available, rooms need to be usable, and the day still needs breathing room. This planner reads a simple scene list and lays it onto a working day so a director or stage manager can see the shape of the call before sending it out.' },
+    { type: 'title', text: 'Make Conflicts Visible Before the Call Goes Out', level: 2 },
+    { type: 'paragraph', html: 'Each scene is checked against the availability windows you enter for its participants and room. The result separates clean sessions from conflicts and scenes that no longer fit the day. It is a planning aid, not a replacement for a production calendar or local working time rules.' },
+    { type: 'title', text: 'Keep Production Notes in the Same Place', level: 2 },
+    { type: 'paragraph', html: 'The call sheet keeps scene notes, participant calls, room calls, and the day overview together. Export the plan as JSON for your own records or print a clean call sheet for the room. Nothing leaves the browser, and the last draft is saved locally on the device.' },
+    { type: 'title', text: 'Privacy and Practical Limits', level: 2 },
+    { type: 'paragraph', html: 'This tool does not send names, schedules, or production notes to a server. It does not manage contracts, confirm legal compliance, or solve overlapping multi-room optimization. Treat the result as a transparent first draft and confirm the final call with the people and rules that govern your production.' },
+    { type: 'stats', items: [
+      { label: 'Tool', value: '1', icon: 'mdi:theater' },
+      { label: 'Rooms', value: 'Any', icon: 'mdi:door-open' },
+      { label: 'Format', value: 'Offline', icon: 'mdi:cloud-off-outline' },
+      { label: 'Privacy', value: 'Local', icon: 'mdi:shield-check' },
+    ] },
+  ],
+};