blocks-uilm

Automate localization workflows against the Blocks UILM API for Next.js and Vite apps.

3|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/SELISEdigitalplatforms/blocks-skills --skill blocks-uilm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blocks-uilm
Source: https://github.com/SELISEdigitalplatforms/blocks-skills/tree/main/skills/blocks-uilm
Command: npx skills add https://github.com/SELISEdigitalplatforms/blocks-skills --skill blocks-uilm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes UI localization for SELISE Blocks by coordinating the UILM v1 API across languages, modules, and keys, including AI-powered translation, file import/export, webhook configuration, and client-side i18n setup.

Core Features & Use Cases

  • Language setup, defaulting, and module creation
  • Translation key management with AI-assisted translation
  • Import/export of translation files and server-generated UILM outputs
  • Webhook configuration and runtime i18n wiring for frontend apps

Quick Start

Initialize Blocks UILM localization by setting up English and German languages and enabling i18n in a sample Next.js app.

Frequently Asked Questions about blocks-uilm

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

FAQPage Schema
How do I automate UI localization workflows for Next.js and Vite apps?

Automate UI localization workflows by coordinating the Blocks UILM v1 API to manage languages, modules, translation keys, and AI-powered translation, then wire runtime i18n directly into your Next.js and Vite frontend applications.

What is the best way to manage multilingual translation keys across frontend modules?

Manage multilingual translation keys by using the Blocks UILM API for centralized module creation and key management, leveraging AI-assisted translation to generate localized UI strings dynamically across your application modules.

Can I import and export translation files using the Blocks UILM API?

Yes, you can import and export translation files using the UILM API endpoints, which handle server-generated UilmFile outputs and manage language, module, and key operations for your localization pipeline.

Does this localization approach support webhook configuration for dynamic module loading?

Yes, this localization approach supports webhook configuration and dynamic module loading, allowing you to trigger automated localization updates and serve client-side i18n strings efficiently across your frontend apps.

How do I set up multiple languages like English and German for my web app?

Set up multiple languages by initializing default languages like English and German through the UILM API, creating corresponding modules, and enabling i18n in your frontend application to serve localized UI strings.

When do I need centralized UI localization instead of static translation files?

You need centralized UI localization when coordinating multilingual UI strings across Next.js and Vite apps with dynamic module loading, requiring AI translation, webhook updates, and server-generated file exports instead of static files.