website-maintainer
Maintain Repomix VitePress Docs
Keeping multilingual documentation consistent across 14 languages is slow and error prone. This skill provides clear paths and rules to update VitePress content and configuration safely.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "website-maintainer". I need to add Italian to the docs. What should I do?
Expected outcome:
- Create a new config/configIt.ts file based on an existing locale config
- Import and add the Italian locale to the main config.ts locales section
- Add search configuration for Italian in configShard.ts
- Create the src/it directory and copy content from src/en as starting point
Using "website-maintainer". Where do I edit the German sidebar navigation?
Expected outcome:
- Open config/configDe.ts in the .vitepress/config directory
- Edit the themeConfig.sidebar section for German navigation structure
- The file controls German-specific navigation labels and menu hierarchy
Using "website-maintainer". How do I update the footer logo across all languages?
Expected outcome:
- Edit config/configShard.ts in the shared configuration
- The footer and logo settings are in themeConfig.footer and themeConfig.logo
- Changes apply to all 14 language locales simultaneously
Security Audit
SafeThis skill contains only documentation and metadata. No executable code, scripts, network calls, or file access capabilities exist. Static findings are false positives triggered by markdown syntax and file path references. The backtick patterns are markdown code block delimiters, not shell execution. No cryptographic functions, network calls, or file operations are present.
Risk Factors
⚙️ External commands (16)
🌐 Network access (1)
📁 Filesystem access (1)
Quality Score
What You Can Build
Plan a new locale
Follow the steps to add a new language with correct config, search, and content folders.
Update a guide
Find the right guide file and update localized content without changing code examples.
Adjust navigation
Edit sidebar and navigation labels in the proper language config file.
Try These Prompts
Show me where to edit the installation guide for Japanese and what file path to open.
List the exact steps to add a new language locale to the VitePress site and which files to create or edit.
Which config file controls sidebar labels for French, and where should I edit them?
Summarize the translation rules and what must remain unchanged when localizing content.
Best Practices
- Keep English as the source of truth for content changes
- Update navigation and sidebar labels in the correct per-language config
- Preserve code examples and CLI options exactly during translation
Avoid
- Editing shared config shard when only one language needs changes
- Modifying code samples or CLI flags while translating text
- Adding a locale without updating search configuration in configShard