agentleFS
Sign inStart free
Mark-LifeMark-Life/peektrace/.agents/skills/effect-ts/SKILL.md

effect-ts

Skill4 starsChanged 3 months agoMITView on GitHub

Comprehensive guide for Effect-TS, the functional TypeScript library. Use when writing Effect programs, defining services, creating layers, handling errors, modeling data with Schema, configuring apps, or testing Effect code. Covers correct APIs, common misconceptions, and idiomatic patterns.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    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
  1. Distinctive:

    Use this to explore APIs, find usage examples, and understand implementation details when the documentation isn't enough.

    line 48
  2. Distinctive:

    If the repository is not present at that path, refer to 01-project-setup.md for clone instructions.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 19 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

Effect-TS Core Patterns

Prescriptive guide for writing idiomatic Effect programs. Source: effect.solutions

Core pattern documents

Load the relevant document based on what you're working on:

  • 01-project-setup.md — Effect Language Service install, editor diagnostics, reference repositories for AI assistance. Load when bootstrapping a new Effect project or setting up tooling.
  • 02-tsconfig.md — Recommended TypeScript compiler settings for Effect (target, module, strict flags, incremental builds). Load when configuring tsconfig.json for an Effect project.
  • 03-basics.md — Effect.gen, Effect.fn, pipe for instrumentation, retry/timeout with Schedule. Load when writing any Effect code or starting a new effectful function.
  • 04-services-and-layers.md — Context.Tag services, Layer.effect/Layer.sync implementations, service-driven development, layer composition with provideMerge, layer memoization. Load when creating services, defining dependency injection, or composing layers.
  • 05-data-modeling.md — Schema.Class records, Schema.TaggedClass variants, branded types, Schema.Union, Match.valueTags, JSON encoding/decoding. Load when defining domain models, DTOs, or data validation schemas.
  • 06-error-handling.md — Schema.TaggedError, catchAll/catchTag/catchTags, expected errors vs defects, Schema.Defect for wrapping unknown errors. Load when defining or handling errors in Effect programs.
  • 07-config.md — Config module, Config layers, ConfigProvider, Schema.Config validation, Redacted secrets. Load when setting up app configuration, environment variables, or config providers.
  • 08-testing.md — @effect/vitest setup, it.effect/it.scoped/it.live, TestClock, providing test layers, worked example with test services. Load when writing or setting up tests for Effect code.
  • 10-incremental-adoption.md — Promise interop (Effect.tryPromise, runPromise), where to introduce Effect first, wrapping external libraries, framework integration (Express/Fastify/Next.js). Load when introducing Effect into an existing non-Effect codebase.
  • 11-http-clients.md — FetchHttpClient, HttpClient.get, HttpClientResponse.schemaBodyJson, typed REST clients with Schema validation. Load when making HTTP requests or building API clients in Effect.
  • 12-observability.md — @effect/opentelemetry, Otlp.layer, spans/logs/metrics export to OTLP collectors. Load when wiring tracing, logging, or metrics for an Effect app.

Local Effect Source

The Effect v4 repository is cloned to ~/.local/share/effect-solutions/effect for reference. Use this to explore APIs, find usage examples, and understand implementation details when the documentation isn't enough.

If the repository is not present at that path, refer to 01-project-setup.md for clone instructions.

Download now (ZIP)

  • Other versions19 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 19

    1. c15t/c15t★ 2ksame name
    2. LodyAI/Lody★ 1.4ksame name
    3. pedronauck/skills★ 641same name
    4. arcboxlabs/linkcode★ 147same name
    5. Effect-TS/skills★ 110same name
    6. PaulRBerg/agent-skills★ 104same name
    7. Kastalien-Research/thoughtbox★ 64same name
    8. joelhooks/effectts-skills★ 43same name
    9. tenequm/skills★ 40same name
    10. vibevalleyhq/vibevalley★ 10same name

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

  • Used alongsideProjects with it also use tanstack, autoresearch and 6 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.
    • barisariburnuSkill

      tanstack

      Expert assistance for TanStack Router, Query (v5), and Table (v8). Use when users need help with file-based routing, type-safe navigation, data loading, search params, queries, mutations, optimistic updates, infinite queries, table state management, or debugging TanStack libraries.

      Also in 3 projects that use this

    • GitHubSkill

      autoresearch

      Autonomous iterative experimentation loop for any programming task. Guides the user through defining goals, measurable metrics, and scope constraints, then runs an autonomous loop of code changes, testing, measuring, and keeping/discarding results. Inspired by Karpathy''s autoresearch. USE FOR: autonomous improvement, iterative optimization, experiment loop, auto research, performance tuning, automated experimentation, hill climbing, try things automatically, optimize code, run experiments, autonomous coding loop. DO NOT USE FOR: one-shot tasks, simple bug fixes, code review, or tasks without a measurable metric.

      Also in 4 projects that use this

    • GoogleSkill

      codebase-design

      Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

      Also in 3 projects that use this

    • VercelSkill

      web-design-guidelines

      Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

      Also in 3 projects that use this

    • Google CloudSkill

      triage

      Gather context on a change or bug and plan the implementation.

      Also in 3 projects that use this

    • GoogleSkill

      improve-codebase-architecture

      Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

      Also in 3 projects that use this

    • +2 more from google
  • In this repository6 other files it gives its agents.

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.

Check your setup, free