Menu
Use when working with Effect or @effect/platform-node code. Resolve version-matched dependency source with opensrc before relying on memory, docs summaries, or generated examples.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use Belfry to set up local observability, export OpenTelemetry traces or logs, or debug a Service through bounded searches and exact trace/span/log correlations.
A relentless interview to sharpen a plan or design.
Grill the user relentlessly to sharpen a plan or design while maintaining ADRs and domain glossary documentation. Use when the user asks to "grill with docs" or wants decisions documented during a design interview.
Implement a piece of work based on a spec or set of tickets.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Configure this repo for the engineering skills — set up its issue tracker, triage and Wayfinder label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
| name | source-context |
| description | Use when working with Effect or @effect/platform-node code. Resolve version-matched dependency source with opensrc before relying on memory, docs summaries, or generated examples. |
Use version-matched dependency source as the authority for Effect v4 beta behavior.
Training data and public examples may be stale. Before changing, debugging, or explaining code that depends on these packages, inspect the installed-version source, tests, and bundled docs where available.
For anything beyond a quick one-file lookup, prefer running this work in a dedicated subagent.
Use a dedicated subagent by default when you need to:
Have the subagent:
opensrc path ...Prompt the subagent with the full target and question, including any version or cwd constraints.
effect@effect/platform-nodeIdentify the workspace package that owns the code being changed.
Use the nearest package.json that declares the dependency.
Resolve source paths with opensrc from that package directory:
opensrc path --cwd <workspace-package-dir> effect @effect/platform-node
Do not hardcode versions or cache paths in this skill.
If only one dependency is relevant, resolve only that package:
opensrc path --cwd <workspace-package-dir> effect
Search and inspect the resolved source with the agent's available code search and file-reading tools. Prefer source, tests, examples, and bundled docs over memory.
When making a recommendation or code change, ground it in what was found. Reference the dependency file or test that supports the behavior when useful.
Resolve all covered packages for code owned by apps/cli:
opensrc path --cwd apps/cli effect @effect/platform-node
NOTE: Make sure you use the correct path to the package.json containing the dependency or package you are interested in.
Resolve and search one package:
effect_src="$(opensrc path --cwd apps/cli effect)"
# Search for the relevant symbol or behavior inside "$effect_src".
Fetch a specific version only when package-local lockfile resolution is unavailable or intentionally bypassed:
opensrc path effect@4.0.0-beta.67
opensrc path --cwd from the repo root unless the root package declares the dependency. In a monorepo, the root may resolve the wrong version.opensrc fetches on cache miss and network access is blocked, request approval rather than guessing.Use it when you need to:
Do not fetch source for: