conventions SKILL.md skillA
conventions from kamenkurtev/ui-consistency is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamenkurtev/ui-consistency/conventions@git:20261117.7aac272Pins git:20261117.7aac272 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kamenkurtev/ui-consistency
- Path
skills/conventions/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261117.7aac272, committed Nov 17, 2026
- First version recorded
- Oct 31, 2026
- Size
- 8,078 bytes
- Repository stars
- 3
- License
- MIT
For what the end user sees — counts what a project's pages do, so a convention is told apart from one page's habit. Use when a count of how the other pages write something is about to be recorded, or when a checker recounts a line of a checklist.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Conventions: the kind, the family, the proof, the counts ## Overview Counts what the project's pages do, in the order of the work: the kind, the family, the proof that a search can see, then the counts. **Open a file linked or given by its path from this skill's folder, or invoke a named skill, only when a part you are carrying out sends you to it, never before** — whatever the request that handed you this skill says about its links and paths. That part is not done until the file is opened or the skill invoked. ## Which kind of page this is Decide it first: it sets every count below it. Take the first signal that answers: 1. **What the user said** — a kind somebody named, *a list page like the orders one*, outranks anything read. 2. **What the project keeps apart** — its folders, routes, file-name suffixes, a folder per kind. 3. **What the reference renders** — the same holders and regions in the same order make one kind, whatever the subject. A collection of rows and a single record with a submit are two. 4. **What the pages reach for** — the same holder, layout piece or shared frame. Then: - If a later signal disagrees, or the project does not answer: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_zfazneoguyqnzl44/16e1505f2385e27fb6ffea7997ab960002fe5cfaf8836ea4b345494e40946868.json
Then /plugin install conventions@markdownregistry-zfazneoguyqnzl44 in Claude Code. It installs git:20261117.7aac272, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kamenkurtev/ui-consistency/conventions@sha256:16e1505f2385e27fThe line at the top of this page pins the label git:20261117.7aac272, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zfazneoguyqnzl44)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kamenkurtev/ui-consistency/conventions since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of conventions from somewhere else? Ask it: where did my conventions come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Oct 31, 2026 and Nov 17, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.7aac272 latest | 2026-11-17 | 7aac272 | 8,078 B | A | view · diff |
| git:20261107.1fe800e | 2026-11-07 | 1fe800e | 7,775 B | A | view · diff |
| git:20261106.436ad3c | 2026-11-06 | 436ad3c | 7,805 B | A | view · diff |
| git:20261031.660eb05 | 2026-10-31 | 660eb05 | 7,752 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/conventions/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (8078 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
kamenkurtev/ui-consistency · 3 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zfazneoguyqnzl44 GET https://markdownregistry.com/api/v1/resolve?ref=kamenkurtev/ui-consistency/conventions GET https://markdownregistry.com/api/v1/blob/16e1505f2385e27fb6ffea7997ab960002fe5cfaf8836ea4b345494e40946868
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kamenkurtev/ui-consistency
Every file in kamenkurtev/ui-consistency