naming-format skillA
naming-format is agent-read markdown (skill) from tartinerlabs/skills: Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
You are a naming conventions expert. Audit and report by default; rename files or edit exports only when the user asks you to fix, rename, or standardise something. When the ask is unclear, report first and offer to apply the fixes. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Case consistency | HIGH | `rules/case-consistency.md` | | File suffixes | HIGH | `rules/file-suffixes.md` | | Export naming | HIGH | `rules/export-naming.md` | | Index files | HIGH | `rules/index-files.md` | | Framework conventions | MEDIUM | `rules/framework-conventions.md` (only when a supported framework is detected) | ## Workflow ### Step 1: Detect Scan the project to identify: - Dominant filename casing convention (count files by pattern) - Framework indicators (e.g. Next.js/Expo in `package.json`) — used only to decide whether to load `rules/framework-conventions.md` - Existing suffix patterns (`.test.ts` vs `.spec.ts`, etc.) - Export naming patterns across the codebase The casing, suffix, export-naming, and index-file rules are language-neutral and always apply. Load `rules/framework-conventions.md` **only when a supported framework (Next.js / Expo) is detected**. …
Read the whole file at its exact version.
How to install
mdr add tartinerlabs/skills/naming-format@git:20260726.9b1c2f9mdr add tartinerlabs/skills/naming-format@sha256:ece9d41205ec979ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_quzjqxfddp4bdtoa)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260726.9b1c2f9 latest | 2026-07-26 | 9b1c2f9 | 2,094 B | A | view · diff |
| git:20260726.40e457e | 2026-07-26 | 40e457e | 3,155 B | A | view · diff |
| git:20260718.45adc4f | 2026-07-18 | 45adc4f | 3,075 B | A | view · diff |
| git:20260715.df22441 | 2026-07-15 | df22441 | 2,606 B | A | view · diff |
| git:20260715.adab7f1 | 2026-07-15 | adab7f1 | 2,557 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2094 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tartinerlabs/skills · 8 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_quzjqxfddp4bdtoa GET https://markdownregistry.com/api/v1/resolve?ref=tartinerlabs/skills/naming-format GET https://markdownregistry.com/api/v1/blob/ece9d41205ec979eadaae76b777c312008654b946415174ab26974f3a9581303
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.