effect
GitHub指导 Effect 框架开发，涵盖 React 状态、HTTP API、CLI 及架构审查。遵循官方文档与仓库规范，聚焦最小化实现，复用现有原语，避免过度设计，确保代码符合业务边界与性能要求。
Trigger Scenarios
Install
npx skills add yielded-dev/auth --skill effect -g -y
SKILL.md
Frontmatter
{
"name": "effect",
"metadata": {
"source": "https:\/\/github.com\/danieljvdm\/dev-kit\/tree\/2bda762e1573fbfdaf5c5aa6c06abe952d812a0b\/skills\/effect-development",
"source_skill": "effect-development",
"source_commit": "2bda762e1573fbfdaf5c5aa6c06abe952d812a0b"
},
"description": "Set up Effect, implement Atom React state, HTTP APIs or CLIs, and review architecture and error handling."
}
Effect development
Read the repository's node_modules/effect/AGENTS.md completely before writing or evaluating Effect code, then follow its relevant links. Installed declarations and repository policy own version-sensitive APIs and verification commands.
Read only the guide for the requested boundary:
- React queries, mutations, shared state, workflows, or SSR: Effect Atom.
- HTTP contracts, handlers, middleware, or server runtimes: HTTP APIs.
- Scripts, CI automation, or command-line applications: CLIs.
- Error propagation, recovery, reporting, or cleanup failures: error handling.
- Trace/log instrumentation and OTLP export: observability, then the shared Effect OTLP snippets.
- A requested architecture review or service-boundary refactor: architecture.
- Adding Effect dependencies or its agent guidance: setup.
For Effect React applications, Effect Atom owns shared state and server data; React renders and dispatches. View-local state can stay in React. Keep business logic in Effect workflows and declare cross-query invalidation as mutation reactivity keys. Read the Atom guide for runtime and registry ownership.
Preserve the requested scope and build the minimum current behavior. Use Effect's existing primitives; a service boundary does not justify extra policy layers, recovery machinery, or configuration for hypothetical uses. Treat the references as guidance for a needed boundary, not a checklist of features to implement. A component edit does not require a server rewrite or architecture audit. Follow repository policy for committed tests; changes to an atom, endpoint, or script do not by themselves justify a new test.
For reusable contracts, use library-first. For critical-path changes or performance claims, use measure-performance. Reuse instructions already loaded and read only the relevant references.
Version History
- 72bfeeb Current 2026-10-18 15:34
