From lokalise-pack
Manage Lokalise secondary workflow: Download translations and integrate with app. Use when downloading translation files, exporting translations, or integrating Lokalise output into your application. Trigger with phrases like "lokalise download", "lokalise pull translations", "export lokalise", "get translations from lokalise".
How this skill is triggered — by the user, by Claude, or both
Slash command
/lokalise-pack:lokalise-core-workflow-bThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Secondary workflow for downloading translations from Lokalise and integrating them into your application.
Secondary workflow for downloading translations from Lokalise and integrating them into your application.
lokalise-install-auth setupRead(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)| Aspect | Workflow A (Upload) | Workflow B (Download) |
|---|---|---|
| Direction | Source -> Lokalise | Lokalise -> App |
| Trigger | Dev adds strings | Build/deploy |
| Format | Any supported | Target format |
| Frequency | On change | On build |
| Error | Cause | Solution |
|---|---|---|
404 Project not found | Wrong project ID | Verify project_id |
Empty bundle | No translations | Check filter options |
Invalid format | Unsupported export | Check format parameter |
Download timeout | Large project | Increase timeout |
See references/implementation-guide.md for detailed examples.
For common errors, see lokalise-common-errors.
npx claudepluginhub ktiseos-nyx/claude-code-plugins-plus-skills --plugin lokalise-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026