renaming-services_skill

Overview

This skill renames a service documentation file and updates every reference across the docs and infrastructure that can cause broken links. It ensures the markdown filename, the services list entry, and nginx redirects are all updated consistently. Use it to convert camelCase to kebab-case, fix typos, or align docs with service slugs in templates.

How this skill works

The skill performs a three-part update: it renames the markdown in docs/services/, updates the slug and icon path in docs/.vitepress/theme/components/Services/List.vue, and adds permanent redirects in nginx/redirects.conf. It also guides you to search and update any remaining internal links and rename related assets like service logos. Finally, it includes a verification checklist to confirm the site and redirects behave correctly locally and in production.

When to use it

• Service name changed in the codebase or templates/compose/
• Fixing camelCase to kebab-case or other slug formatting
• Correcting typos or consolidating duplicate service docs
• Adding versioned or compound service slugs (e.g., mautic5, ente-photos)
• Removing or renaming deprecated services while preserving redirects

Best practices

• Always update all three locations: docs/services/, List.vue, and nginx/redirects.conf to avoid 404s
• Use lowercase and hyphens for filenames (kebab-case) and match the authoritative service slug
• Keep 301 redirects even for deleted pages to preserve SEO and bookmarks
• Run a repository-wide search for the old slug and update any internal links you find
• Verify changes locally at http://localhost:5173 and confirm old URLs redirect to the new paths

Example use cases

• Rename denoKV to denokv.md and update List.vue and nginx redirects
• Fix service slug typo from old-name to new-name across docs and redirects
• Consolidate two docs into ente-photos.md and add redirects from the former filenames
• Add a versioned service page like mautic5.md and update the services list and redirects