What do I need to use Filename Convention?

The file population; The sort need; Cloud-doc reality; The current chaos sample.

Is Filename Convention free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Filename Convention

Q: How do I know the Filename Convention output is good?

The skill verifies itself against its own quality checks: The lead slot matches the team's dominant retrieval pattern; Slot order is fixed and separator discipline is stated; "final" is banned with its printed justification; Examples use the team's real files, not invented ones.

🔵 Stable🕐 updated 2026-07-19 🔷 SkillSpec L3 pm-cowork

Set a filename convention that sorts, searches, and survives — date-first ISO format, the descriptor grammar, version suffixes that end the FINAL-final2 era, and the rollout that gets a team actually using it. Use when asked set up file naming rules, our filenames are chaos, what should we call our files, or fix the v2-final-FINAL problem. Produces the convention with its grammar, examples for the team's real file types, the version rule, and the one-line cheat sheet.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸The file population — what the team actually produces (contracts, decks, exports, meeting docs); the grammar's slots come from what needs distinguishing

▸The sort need — chronological (date-first) vs. entity-first (`acme_2026-07-19_...` when browsing-by-client dominates); the retrieval pattern picks the lead slot

▸Cloud-doc reality — Google Docs/Notion pages need the convention too (titles are names); versioned-by-platform files relax the version suffix

▸The current chaos sample — a dozen real filenames; the before/after table is the convention's best salesman

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓The lead slot matches the team's dominant retrieval pattern

✓Slot order is fixed and separator discipline is stated

✓"final" is banned with its printed justification

✓Examples use the team's real files, not invented ones

✓Rollout is new-files-plus-drain, never mass rename

⚠️ What it refuses to do

Do not allow DD-MM vs MM-DD ambiguity — ISO or chaos, there is no third option

Do not encode what the folder already says — `Clients/Acme/acme-acme-contract` wastes a slot

Do not permit "final" even once — it's the gateway drug to FINAL-final2

Do not design slots for files the team doesn't produce — grammar bloat kills adoption

Do not mass-rename history — links break; the drain rule gets there without the breakage

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="filename-convention"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Filename Convention is one of 750 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog