effect-ts

Topics in the source

• Effect 4
• Workflow
• Evidence Order
• Reference Router
• Boundaries

Apply Effect 4 semantics from project-local architecture, the narrowest relevant reference, and source matching the target's installed packages. Do not activate this workflow merely because a file imports effect. For nontrivial Effect work: 1. Resolve the target package or workspace and its exact installed effect and relevant @effect/ versions. If effect is not 4.x, stop because this skill does not apply. For 3.x, point the user to the v3 skill: npx skills add PaulRBerg/agent-skills#shelved --skill effect-ts-v3. 2. Confirm lockstep versions: every @effect/ package must match the installed effect version exactly. Report a mismatch instead of coding around it. 3. Inspect neighboring services, layers, errors, schemas, runtime boundaries, and tests. Local conventions decide organization. Installed package evidence decides API facts. 4. Read references/critical-rules.md, then only the task-specific references below. 5. Verify every uncertain import, signature, or behavior against the package installation visible to the target workspace before editing. Do not port v3 names from memory. Many were renamed or removed. 6. Implement the smallest pattern consistent with the project and run the

This is an excerpt. Refer to the complete source and its current requirements.