Effect Schema
Effect Schema as the one validation and typing layer for data crossing a trust boundary (requests, config, storage, third-party and LLM output), with branded ids, tagged errors, JSON Schema for tools, and round-trip plus property tests.
Category: tooling
In your existing repository
Ask your agent to check compatibility, follow this fragment’s brief, and verify the resulting project. What happens next
- Applies to:
- astro-blog, astro-fullstack, cloudflare-react-router, mobile-expo, python-react, react-router, tauri-react, typescript-api, typescript-cli
Add to your project
Paste the prompt into the coding agent working on your project.
View prompt
Or use the terminal
npx @steamfield/stacks add effect-schema| Step | Phase | Layer | Command |
|---|
No additional verify steps declared. Run the project’s existing verification after applying the brief.
Use with a new stack
Starting fresh instead? These stacks support this fragment.
- astro-blogoptional
npx @steamfield/stacks new astro-blog --with effect-schema - astro-fullstackoptional
npx @steamfield/stacks new astro-fullstack --with effect-schema - mobile-expooptional
npx @steamfield/stacks new mobile-expo --with effect-schema - python-reactoptional
npx @steamfield/stacks new python-react --with effect-schema - cloudflare-react-routeroptional
npx @steamfield/stacks new cloudflare-react-router --with effect-schema - react-routeroptional
npx @steamfield/stacks new react-router --with effect-schema - tauri-reactoptional
npx @steamfield/stacks new tauri-react --with effect-schema - typescript-clioptional
npx @steamfield/stacks new typescript-cli --with effect-schema - typescript-apioptional
npx @steamfield/stacks new typescript-api --with effect-schema
Alternatives in tooling
- Effect testing and API skill
Effect testing with @effect/vitest (fresh real layers per test, TestClock instead of sleeps, typed failure and defect assertions), shipped Effect guidance for each agent, and an agent skill written from the installed Effect release's declarations.
Also applies to: astro-blog, astro-fullstack, mobile-expo, python-react, cloudflare-react-router, react-router, tauri-react, typescript-cli, typescript-api
- Git hooks (lefthook)
lefthook git hooks that format and lint staged files, enforce Conventional Commits, and run the project's tests before push.
Also applies to: astro-blog, astro-fullstack, mobile-expo, python-react, cloudflare-react-router, react-router, tauri-react, typescript-cli, typescript-api
- OpenTelemetry (OTLP) for Effect servers
OpenTelemetry traces, logs and metrics over OTLP for the Effect server in typescript-api, astro-fullstack and react-router. One observability layer adds trace ids to the existing logs, exports nothing without an endpoint, and is tested with an in-memory tracer and a loopback OTLP receiver.
Also applies to: astro-fullstack, react-router, typescript-api
- REST resource conventions
Agent rules for naming and shaping HTTP resources (plural nouns, methods and status codes, one resource shape, cursor pagination, versioning), independent of framework and layout, plus an AGENTS.md section recording the project's choices.
Also applies to: astro-fullstack, mobile-expo, python-react, typescript-api
- rr remote test runner
Configures rr (github.com/rileyhilliard/rr) so the project's test, lint, and build commands can run on remote machines over SSH, with a committed .rr.yaml of named tasks, an AGENTS.md section, and the rr Claude Code plugin.
Also applies to: astro-blog, astro-fullstack, mobile-expo, python-react, cloudflare-react-router, react-router, tauri-react, typescript-cli, typescript-api
Files
This fragment supplies instructions rather than project files.
Usage
Among stacks projects in the 28 days through 30 Oct 2026: Project count: not enough runs yet; Green rate: not enough runs yet.
Weekly projects by stack
Projects whose final fragment set included this fragment, grouped by stack.
Not enough runs in this breakdown yet.
Stacks projects per UTC week through 30 Oct 2026. Published stack counts only.
By stack
How often this fragment stays in a default composition, or gets attached as an option.
Not enough runs in this breakdown yet.
Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.
Green rate with and without it
This compares projects; it isn't an effect of the fragment.
Not enough runs in this breakdown yet.
Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.
Often used with
Co-occurrence above the baseline, within a stack. Required fragment pairs are excluded.
Not enough runs in this breakdown yet.
Stacks projects · 28 days through 30 Oct 2026. Counts rounded to 5.
Computed 31 Oct 2026, through 30 Oct 2026. Numbers describe stacks projects, not the ecosystem.