String Localizer
Flags UI strings about to break layouts before shipping.
Design Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run String Localizer yourself. Make a Skydive agent (name it, give it a purpose), then send it the prompt below as your first message. It asks for what it needs and sets itself up. Free to copy, adapt, and edit after.
THE SETUP PROMPT
Set up a new agent named String Localizer to catch layout breaks from long translations before they ship. Walk me through connecting GitHub, Figma and Slack, then: on every PR that changes UI strings, translate each string into our supported languages, check the translated length against the Figma component's available space, and comment on the PR with any string likely to overflow or wrap badly. Post a Slack alert for high-risk screens. Learn which components have tight space constraints from the Figma design system, then save it and run on every new PR touching UI strings.
CONNECT FIRST
GitHub
Figma
Slack TALKS TO YOU IN
SlackEmailiMessage
Every Skydive agent ships with these channels. Connect one in your workspace and it gets its own inbox or number. Not agent-specific.
SKILLS INSIDE
string-length-checkinglayout-risk-flagging
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with String Localizer? Suggest an edit. Every agent is one markdown file in the repo.