coding-standards
Skill4 starsChanged 5 days agoMITView on GitHub
Apply effect-durable-agent's TypeScript, Effect and testing rules when writing, changing or reviewing code here, and the check a diff must pass before commit.
120 other projects use a version of this.
Adopted by
Most recently taken up by
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- lhbsaa/apex-unifiedtheir own version, first seen Nov 8, 2026
- ahmadvahidi/skill-atlastheir own version, first seen Nov 8, 2026
- n1kben/agentstheir own version, first seen Nov 8, 2026
- shinpr/ai-coding-project-boilerplatetheir own version, first seen Nov 8, 2026
- Lukk17/agent-standardstheir own version, first seen Nov 7, 2026
Used with
Projects with it also use everything-claude-code, everything-claude-code-conventions and 10 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.
InfopibeSkilleverything-claude-code
Also in 9 projects that use this
mryeastcodeSkilleverything-claude-code-conventions
Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.
Also in 8 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 8 projects that use this
tpavanipradeepSkillnextjs-turbopack
Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.
Also in 15 projects that use this
CodeWithBehnamSkilldmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
Also in 17 projects that use this
InfopibeSkillinvestor-outreach
Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
Also in 22 projects that use this
- +1 more from Infopibe
Other versions120 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 120
- affaan-m/ECC★ 246ksame name
- dotnet/winforms★ 4.9ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- sjjian/openhare★ 816same name
- dmmulroy/skills★ 428same name
- nanvix/nanvix★ 318same name
- loulanyue/awesome-claude-notes★ 272same name
- shinpr/ai-coding-project-boilerplate★ 236same name
- kid-sid/claude-spellbook★ 190same name
110 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 repository3 other files it gives its agents.
- project-contextSkill
- releaseSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 104 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Public surface: Every export is a contract across all three packages.
- Very specific: line 30
Changelog: Every user-visible change adds an entry under the next version in CHANGELOG.md, marks breaking items Breaking:, and states the …
“Common” is measured: kept by at least 6 in 10 of the 104 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
Coding standards
Status: implemented
These specialize the principle leaves and typescript-best-practices for this repository.
- Effect v4, one aligned minor.
effect,@effect/ai-*and@effect/vitestare pinned exactly as devDependencies (4.1.2) and allowed patch releases as peers (~4.1.2). Effect AI and HTTP are@stability unstableupstream, so a new Effect minor is an EDA release (releasing). Upgrade the whole aligned set together and record it inUPGRADE_LOG.md. - Toolchain. TypeScript 7 (tsgo), Vite+ (
vp fmt,vp pack,vp test) and oxlint with--deny-warnings.mise run installpatches oxlint for Effect diagnostics; run it before linting. The repository's own oxlint rules live inpackages/effect-durable-agent/tooling/oxlintand ship with the core package. - Tests. Pick the archetype and owning suite from testing before
adding a test; extend the owner (scenario corpus, generator, crash-prefix sweep, journey) rather
than adding a named regression. Do not import
@effect/vitestunder Vite+; useTestClockfor time. The default suite never needs a network or provider key. - Durable formats. A new event field is optional and decoded with retained excess; never
rewrite stored events. A transcript interpretation change bumps
transcriptSemanticRevisionand re-records fingerprints (UPDATE_TRANSCRIPT_FINGERPRINTS=1). - Public surface. Every export is a contract across all three packages. Adding a subpath means
updating its
exportsmap; removing or narrowing one is a breaking change for the changelog. - Changelog. Every user-visible change adds an entry under the next version in
CHANGELOG.md, marks breaking items**Breaking:**, and states the storage, protocol and API impact.
Gate before commit: mise run ci passes. It is what .github/workflows/ci.yml runs on every
pull request and every push to master.
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.

