jralvarenga/combined
skills/combined/SKILL.md
Guide for combining Better Translate packages without duplicating translation ownership.
$ install --global
skillsauthnpx skillsauth add jralvarenga/better-translate combinedInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 1:16 PM31.6s1 file scanned
SKILL.md
- name:
- combined
- description:
- Guide for combining Better Translate packages without duplicating translation ownership.
Combined Skill
Use this guide when the app needs more than one Better Translate package.
Common combinations
React app
@better-translate/core@better-translate/react
Next.js App Router with server translations only
@better-translate/core@better-translate/nextjs
Next.js App Router with server and client translations
@better-translate/core@better-translate/nextjs@better-translate/react
TanStack Router app with React UI
@better-translate/core@better-translate/tanstack-router@better-translate/react
Astro docs site with localized markdown
@better-translate/core@better-translate/astro@better-translate/md
Any app with AI-generated locale files
Add @better-translate/cli to any combination above when you want the CLI to manage locale file creation.
Example - Next.js app with generated translations:
@better-translate/core@better-translate/nextjs@better-translate/cli
Keep TypeScript autocomplete available
Every combination still works best when one shared exported translator stays the source of truth. Let adapters, hooks, and helpers read from that same typed translator instead of recreating locale rules in multiple places.
Rule to keep the setup clean
Every combination still has one source of truth:
- core owns the translator
- framework adapters own routing or request integration
- react owns hooks and providers
- md owns localized content loading
- cli owns generation
Do not duplicate locale rules in multiple places.
Related Skills
jralvarenga/workspace
documentation
VerifiedTrustedCommunity
Repository map for finding Better Translate packages, docs, and examples.
23SKILL.mdUpdated Apr 23, 2026
jralvarenga/status
tools
VerifiedTrustedCommunity
Snapshot of the current public Better Translate package and adapter surface.
23SKILL.mdUpdated Apr 23, 2026
jralvarenga/rtl
documentation
VerifiedTrustedCommunity
Right-to-left locale configuration guide for Better Translate.
23SKILL.mdUpdated Apr 23, 2026
jralvarenga/react
development
VerifiedTrustedCommunity
React and Expo integration guide for Better Translate providers, hooks, and typed translation access.
23SKILL.mdUpdated Apr 23, 2026