agentleFS
advaitadvait/effect-durable-agent/.agents/skills/coding-standards/SKILL.md

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

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.
  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • niloykumarbarmanSkill

    agent-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

  • tpavanipradeepSkill

    nextjs-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

  • CodeWithBehnamSkill

    dmux-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

  • InfopibeSkill

    investor-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

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
  1. Very specific:

    Public surface: Every export is a contract across all three packages.

    line 28
  2. Very specific:

    Changelog: Every user-visible change adds an entry under the next version in CHANGELOG.md, marks breaking items Breaking:, and states the …

    line 30

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/vitest are pinned exactly as devDependencies (4.1.2) and allowed patch releases as peers (~4.1.2). Effect AI and HTTP are @stability unstable upstream, so a new Effect minor is an EDA release (releasing). Upgrade the whole aligned set together and record it in UPGRADE_LOG.md.
  • Toolchain. TypeScript 7 (tsgo), Vite+ (vp fmt, vp pack, vp test) and oxlint with --deny-warnings. mise run install patches oxlint for Effect diagnostics; run it before linting. The repository's own oxlint rules live in packages/effect-durable-agent/tooling/oxlint and 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/vitest under Vite+; use TestClock for 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 transcriptSemanticRevision and re-records fingerprints (UPDATE_TRANSCRIPT_FINGERPRINTS=1).
  • Public surface. Every export is a contract across all three packages. Adding a subpath means updating its exports map; 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.