podverse-documentation-conventions

What problem does it solve?

Documentation at Podverse often suffers from inconsistent file naming, ambiguity about which files belong to which docs, and difficulty locating the correct Markdown docs across the monorepo. This skill defines a set of naming conventions that enforce unique, full-path-based file names to reduce confusion and improve discoverability.

Core Features & Use Cases

• Enforces one documentation file per directory by naming files after their full path (e.g., APPS-API.md for apps/api).
• Ensures consistent, predictable navigation and search results across root docs and directory-specific docs.
• Supports migration and onboarding tasks by providing a clear, scalable naming scheme for new documentation.

Quick Start

Follow the directory-wide naming conventions when creating or renaming documentation files.