markdown-naming

Standardize Markdown file names to kebab-case for .md and .mdc files.

37|20|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill markdown-naming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdown-naming
Source: https://github.com/fieldsphere/cursor-team-marketplace-template/tree/main/plugins/cursor-starter-pack/skills/markdown-naming
Command: npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill markdown-naming

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent naming across Markdown files leads to confusion and makes discovery harder; this Skill defines a standard for file names to improve navigation and maintainability.

Core Features & Use Cases

  • Enforces kebab-case naming for all Markdown files (.md, .mdx, .mdc) across repositories.
  • Provides clear guidelines for naming rules, agents, commands, and documentation files to ensure uniform structure.
  • Use Case: When adding a new Cursor Starter Pack skill or editing existing docs, apply the naming conventions to keep files discoverable and predictable.

Quick Start

Rename new or renamed Markdown files to kebab-case following the patterns described in this guide.

Frequently Asked Questions about markdown-naming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Markdown file naming conventions across a repository?

Apply kebab-case naming to all .md, .mdx, and .mdc files. This standardization ensures repository documentation remains predictable, easily searchable, and consistently organized across project folders and notes.

What naming convention should I use for documentation files to improve discoverability?

Use kebab-case for documentation files to maximize discoverability. Lowercase words separated by hyphens create uniform file names that are easier to search, index, and maintain across large project repositories.

Can I convert existing Markdown files to kebab-case without breaking repository links?

Converting existing Markdown files to kebab-case requires updating internal repository links. Use explicit naming patterns and guidance to rename files while maintaining consistent navigation and documentation structure.

Does this Markdown naming convention apply to .mdc files and Cursor Starter Pack components?

Yes, the kebab-case naming convention applies to .mdc files and Cursor Starter Pack components. It specifies explicit naming patterns for rules, agents, commands, and documentation to maintain uniform structure across all formats.

What is the best way to validate Markdown file naming consistency in a project?

Validate Markdown file naming consistency using built-in validation checks. These checks enforce kebab-case usage across .md and .mdc files, ensuring all repository documentation follows the standardized nomenclature.