Add a new language to a Next.js application using next-intl internationalization.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add github/awesome-copilot --skill next-intl-add-languageCompatible with
Supported agents
Requires translating all entries from en.json in the ./messages directory to the new language
Update routing configuration in src/i18n/routing.ts and middleware in src/middleware.ts to recognize the new language
Register the language in the language toggle component at src/components/language-toggle.tsx
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnext-intl-add-languageExecute the skills CLI command in your project's root directory to begin installation:
epx add github/awesome-copilot --skill next-intl-add-languageFetches next-intl-add-language from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/next-intl-add-language
Restart Cursor to activate next-intl-add-language. Access via /next-intl-add-languagein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
java-springboot
github/awesome-copilot · Backend · same repo
frontend-design
anthropics/claude-code · Frontend · same category
antigravity-design-expert
sickn33/antigravity-awesome-skills · Frontend · same category
frontend-ui-ux
code-yeongyu/oh-my-opencode · Frontend · same category
emil-design-eng
emilkowalski/skill · Frontend · same category
karpathy-guidelines
forrestchang/andrej-karpathy-skills · Frontend · same category
We added next-intl-add-language from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
next-intl-add-language fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in next-intl-add-language — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for next-intl-add-language matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: next-intl-add-language is focused, and the summary matches what you get after install.
next-intl-add-language reduced setup friction for our internal harness; good balance of opinion and flexibility.
next-intl-add-language fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added next-intl-add-language from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
next-intl-add-language has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added next-intl-add-language from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 37