IMS Naming Mismatch and Linter False Positives on Skill Names

Context

While building the support plugin for Help Center content pipeline skills (SPEC-007 in S003-VisiMatch-Help-Center), the toolkit linter flagged every new skill with warnings like:

The skill name 'vt-su-hc-content-create' should match the folder name 'hc-content-create'.

Investigation revealed this is not a bug in the new skills — the same pattern exists in the IMS plugin (ims-intake folder, vt-i-intake name) and was never caught because those skills predate the linter.

Observation

Two separate but related issues:

1. The IMS plugin should be called VMS — "IMS" (Integriertes Managementsystem) is generic. The plugin implements the VisiTrans Management System specifically. Team internally refers to it as VMS. The "IMS" name creates confusion, especially as more plugins are added.

2. Skill naming convention has an undocumented prefix pattern — Skills use vt-{area}-{name} in the name: field but the folder uses just {plugin}-{name}. This is intentional (prefix scopes skills by domain in Claude Code's skill list) but the linter doesn't know about it.

Decision

Created intake proposal: intake/pending/from-projects/2026-03-27-ims-to-vms-rename-and-skill-naming-convention.md

This should be addressed as a coordinated rename + linter fix in a dedicated sprint, not as a side-effect of another spec.

Learning

When creating new plugins, the naming convention friction surfaces immediately. Documenting the prefix convention and updating the linter should happen before adding more plugins — otherwise every new plugin will trigger the same false positives.