Naming Kiro skills consistently with existing patterns improves discoverability

I was about to create a skill for static page creation and initially named it add-page. Then I looked at the existing skills — content creation ones all followed a {type}-guide pattern: post-guide, til-guide.

add-page starts with a verb, which groups it with action-oriented skills like fix-lint and debug-build. But page-guide immediately signals "content creation guide" alongside its siblings:

# Content creation ({type}-guide)
post-guide
til-guide
page-guide     ← fits naturally here
 
# Actions ({verb}-{target})
fix-lint
debug-build
run-tests

Skill naming matters beyond aesthetics. Agents use the name and description fields for auto-selection, but consistent naming patterns also help humans scan and manage the skill directory without second-guessing where things belong.