uinaf/effect-ts
Implement, debug, refactor, migrate, review, or explain Effect TypeScript code. Use when a task touches `effect` or `@effect/*` APIs, especially services, layers, schemas, runtime wiring, platform or CLI packages, Effect testing, or Promise-to-Effect migration.
98
100%
Does it follow best practices?
Impact
93%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Evaluation results
100%
16%Task: Audit and Fix an Effect TypeScript Project Setup
Removed @effect/schema
100%
100%
Single platform package
100%
100%
Test framework added
50%
100%
strict: true set
100%
100%
exactOptionalPropertyTypes
100%
100%
verbatimModuleSyntax
100%
100%
noUnusedLocals
0%
100%
noImplicitOverride
0%
100%
Language service plugin
100%
100%
language-service in package.json
100%
100%
VS Code workspace TypeScript
75%
100%
Audit report completeness
100%
100%
Node module settings
100%
100%
79%
-2%Task: Implement a Notification Service
Context.Tag usage
100%
75%
Readonly methods
100%
100%
Effect.fn for service method
0%
0%
Tagged error types
100%
100%
Domain model variants
57%
85%
Layer graph for dependencies
100%
100%
No runPromise in service
100%
100%
No globals
100%
100%
Test layer provided
0%
0%
send method environment
100%
100%
No Promise returns in service
100%
100%
Error channel specificity
100%
100%
Barrel export correctness
100%
60%
100%
24%Task: Migrate a Third-Party SDK Integration to Effect
use pattern applied
0%
100%
AbortSignal preserved
100%
100%
Tagged error conversion
100%
100%
No runPromise in service
100%
100%
Effect.tryPromise used
0%
100%
ManagedRuntime in app.ts
100%
100%
No async/yield mixing
100%
100%
Service Context.Tag
100%
100%
Layer graph used
100%
100%
Error types structured
100%
100%
Barrel export correctness
100%
100%
use pattern appropriate use
0%
100%
- Evaluated
- Agent
- Claude
- Model
- Claude Sonnet 4.6