Vision
Prismy embraces your coding flow and super-charges it. AI agents will try to translate your app themselves. These skills make sure they do it right: respecting your glossary, following your guidelines, and never bypassing your translation engine. Prismy keeps these skills aligned with the latest AI assistant standards and i18n best practices, so you don’t have to.More skills are coming. Have an idea or feedback? Let us
know.
Source on GitHub
Available Skills
i18n-translate
Generates translations locally via the Prismy CLI after your assistant modifies source keys. Skip this skill if you prefer triggering translations from your PR/MR instead.Requires Prismy CLI and an API key.
i18n-respect-copywriting-guidelines
Fetches your glossary and wording instructions from Prismy before the AI writes any user-facing copy. Keeps every string on-brand and consistent.Requires Prismy CLI and an API key.
i18n-detect-hardcoded
Scans code changes for hardcoded strings (labels, headings, error messages, etc.) and flags them for extraction into locale files.Generic skill. No Prismy account needed.
i18n-enforcing-source-language-only
Prevents the AI from editing target-language locale files. Translations come from your translation engine, not from the AI guessing.Generic skill. No Prismy account needed.
Installation
Prerequisites
Some skills require the Prismy CLI (see each skill’s description above). If you only install generic skills like i18n-detect-hardcoded or i18n-enforcing-source-language-only, no CLI setup is needed. For skills that use the CLI:Install all skills
Install specific skills
Every skill is optional. Pick only what you need:Recommended combination
For most projects using Prismy, install the translation workflow, copywriting guidelines, and the source-only guard:How to Use
Once installed, the skills work automatically. There is nothing to configure in your code. Your AI assistant picks them up and follows their instructions as it writes code. Here is what changes in practice:- You prompt your AI assistant as usual (“add a signup button”, “refactor this component”, etc.).
- The assistant detects which skills are installed and applies them in the background.
- Depending on the skills you have:
- Hardcoded strings are flagged and extracted to your locale files.
- Target-language files are left untouched.
- New copy follows your glossary and brand guidelines.
- Translations are generated locally via
prismy generate.
GitHub & GitLab Integration
AI agent skills are fully compatible with Prismy’s GitHub and GitLab integrations. They cover different moments of your workflow:- Skills act during local development, while your AI assistant is writing code.
- GitHub / GitLab integration acts when you push or open a PR/MR, letting you trigger translations via a comment.
| Approach | How translations are generated |
|---|---|
| With i18n-translate skill | Your AI assistant runs prismy generate locally after editing source keys. Translations are ready before you push. |
| Without i18n-translate skill | You push your changes and trigger translations directly from the PR/MR with a comment. |
FAQ
Which AI coding assistants are supported?
Which AI coding assistants are supported?
The skills are compatible with any assistant that supports the agent skills
standard, including Claude Code, Cursor, GitHub Copilot, and
similar tools.
Do I need a Prismy account?
Do I need a Prismy account?
Not necessarily. i18n-detect-hardcoded and i18n-enforcing-source-language-only are generic i18n best-practice skills that work on any project without a Prismy account.i18n-translate and i18n-respect-copywriting-guidelines require the Prismy CLI and an API key, since they call Prismy’s services.
Are the skills mandatory?
Are the skills mandatory?
No. Every skill is entirely optional and independent. Install only the ones
that match your workflow. You can always add or remove skills later.
Do skills modify my translation files directly?
Do skills modify my translation files directly?
The i18n-translate skill calls the Prismy CLI to generate translations.
The i18n-enforcing-source-language-only skill actively prevents the AI
from editing target-language files directly. Your translations always go
through your translation engine, not the AI.
Will skills conflict with the GitHub/GitLab integration?
Will skills conflict with the GitHub/GitLab integration?
No. They complement each other. Skills handle the local development phase,
while the GitHub/GitLab integration handles the CI/PR phase. See the section
above for details.
Where is the source code?
Where is the source code?
The skills are open source and available on GitHub:
prismy-io/prismy-agent-skill.
Licensed under MIT.