| name | effect-schema |
| description | Use when working with effect/Schema, tagged errors, decode/encode boundaries, or Effect beta compatibility. |
| license | MIT |
| compatibility | opencode |
| metadata | {"domain":"effect-schema","repo":"alchemy-azure"} |
Effect Schema
Use this skill for effect/Schema modeling, tagged errors, and beta compatibility.
Current Compatibility Note
This repo tests with alchemy@2.0.0-beta.57 and effect@4.0.0-beta.84, while accepting stable Effect 4 through the peer dependency range.
Rules
- Treat schemas as
Schema<Type, Encoded, Requirements>.
- Decode untrusted API/config data at boundaries.
- Prefer tagged errors for provider failures that callers may handle.
- Keep TypeScript types and runtime validation aligned.
- Verify exact Schema APIs against docs/source when changing Effect versions.
Useful References
- Effect Schema docs:
https://effect.website/docs/schema/introduction/
- Effect changelog/source for beta compatibility.
@alchemy-effect for Alchemy v2 provider/resource integration details.