project-conventions
Skill7 starsChanged 23 days agoNo licenceView on GitHub
Learn an existing codebase before changing it, then match its conventions, write human-readable self-documenting code without added comments, and reuse what already exists. MUST be used before implementing meaningful changes in an existing project, and when creating any component, route, endpoint, server function, hook, query, validation helper, or utility. Also use when new code could plausibly duplicate an existing implementation.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- github/squadtheir own version, first seen Nov 8, 2026
- microsoft/github-vteam-industry-demostheir own version, first seen Oct 25, 2026
- g-cqd/skillstheir own version, first seen Oct 23, 2026
- vishalguptax/agent-engineering-kittheir own version, first seen Oct 11, 2026
- hyperledger-labs/splicetheir own version, first seen Oct 9, 2026
- TangleML/tangle-uitheir own version, first seen Oct 8, 2026
Used with
Projects with it also use e2e-template-testing, notification-routing and 9 more.
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.
GitHubSkille2e-template-testing
End-to-end validation of coordinator and agent template changes
Also in 3 projects that use this
- GitHubSkill
notification-routing
Route agent notifications to specific channels by type — prevent alert fatigue from single-channel flooding
Also in 3 projects that use this
Microsoft AzureSkillcoordinator-source-of-truth
The complete file-by-file source-of-truth hierarchy for Squad: which files are authoritative, which are derived/append-only, who may write each one, who may read each one, and the precedence rules when they conflict. Squad coordinator loads this on demand when it needs to resolve a write conflict, decide where a piece of state belongs, or answer a 'who owns this file' question.
Also in 3 projects that use this
- Microsoft AzureSkill
cross-squad-communication
Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
- +4 more from github
- +2 more from Azure
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- github/gh-aw★ 5.6ksame name
- github/squad★ 3.4ksame name
- Soju06/codex-lb★ 3.3ksame name
- nextcloud/notes-android★ 1.1ksame name
- hyperledger-labs/splice★ 122same name
- TangleML/tangle-ui★ 104same name
- Azure/apiops-cli★ 32same name
- choi138/toki★ 9same name
- batin/five-guys★ 2same name
- g-cqd/skills★ 2same name
7 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.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/gentjin.mdcCursor rule
- api-designSkill
- architecture-reviewSkill
- backend-reviewSkill
- cleanupSkill
- compactionSkill
- database-reviewSkill
- dependency-reviewSkill
- deployment-readinessSkill
- frontend-reviewSkill
- git-workflowSkill
- incident-responseSkill
- integration-reviewSkill
- knowledge-vaultSkill
- performance-reviewSkill
- refactoring-migrationSkill
- reportingSkill
- requirements-reviewSkill
- review-orchestratorSkill
- security-reviewSkill
- skill-authoringSkill
- systematic-debuggingSkill
- test-strategySkill
- work-in-progressSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
21 rules. 0 are common, 19 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 11 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.
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.