conventions
Skill2 starsChanged 55 days agoMITView on GitHub
Applies the shared TypeScript, markdown, testing, security, and language rules. Use when writing or reviewing code, tests, or markdown, or when asked whether something follows the house style.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- MohammadShehadeh/agent-skillstheir own version, first seen Nov 1, 2026
- piomin/claude-ai-spring-boottheir own version, first seen Oct 25, 2026
- scottlivingston/claude-skillstheir own version, first seen Oct 25, 2026
- wuyining0130/c-roomtheir own version, first seen Oct 15, 2026
- philtzjp/skillstheir own version, first seen Oct 13, 2026
- kamenkurtev/ui-consistencytheir own version, first seen Oct 11, 2026
Used with
Projects with it also use release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- meteor/meteor★ 45ksame name
- piomin/claude-ai-spring-boot★ 1.4ksame name
- psenger/ai-agent-skills★ 10same name
- yyyyolo7a79-sketch/claude-conventions-skill★ 3same name
- MohammadShehadeh/agent-skills★ 2same name
- philtzjp/skills★ 2same name
- psenger/catholic-ai-skills★ 2same name
- yacb2/aidex★ 2same name
- kamenkurtev/ui-consistency★ 1same name
- mauroepce/claude-workspace★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
When writing, follow the rules as you go.
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Conventions
The files in rules/ are the house style. When a rule conflicts with the project's AGENTS.md,
the project wins.
1. Load the rules that apply
| Rule | Applies to |
| plain-language | Always: anything a person reads |
| security | Always: secrets, trust boundaries, shell use |
| usa-english | Always: spelling |
| user-questions | Always: questions to the user go through ask |
| code-style | .ts, .tsx, .vue |
| jsdoc | .ts, .tsx. The jsdoc skill has the formats |
| testing | Test files |
| markdown | .md, .mdx. documentation and humanizer cover voice and SEO |
The path-scoped rules load on their own through paths: frontmatter. Open one by hand only when
it has not loaded.
2. Apply or review
When writing, follow the rules as you go. When reviewing, check the file against each loaded rule.
Output
For a review, one bullet per finding, grouped by file with the most important first: path:line,
the rule, the change. Then one bullet naming what you checked and found fine, so the reader knows
the review covered it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.