source-context
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.
- License 许可
- MIT
- 所属仓库
- endalk200/belfry
- 最近更新
- 2026-10-23
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- 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.
03 SKILL.md 正文
Purpose
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:
- Inspect multiple files
- Trace call paths across a library
- Compare runtime code and tests
- Verify edge-case behavior
- Investigate version-specific behavior
- Summarize findings without dumping raw source into the main thread
Have the subagent:
- Resolve the correct source tree with
opensrc path ... - Inspect the fetched code with normal search and read tools
- Return only the relevant files, symbols, and conclusions
Prompt the subagent with the full target and question, including any version or cwd constraints.
Packages Covered
effect@effect/platform-node
Required Workflow
-
Identify the workspace package that owns the code being changed. Use the nearest
package.jsonthat declares the dependency. -
Resolve source paths with
opensrcfrom that package directory:opensrc path --cwd <workspace-package-dir> effect @effect/platform-nodeDo 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.
Usage Examples
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
Important Notes
- Do not run
opensrc path --cwdfrom the repo root unless the root package declares the dependency. In a monorepo, the root may resolve the wrong version. - If
opensrcfetches on cache miss and network access is blocked, request approval rather than guessing. - If source and local package types disagree with public docs, trust the installed-version source/types.
When to Use
Use it when you need to:
- Modify code importing these packages
- Debug runtime or type behavior involving these packages
- Understand behavior that docs or types do not explain
- Understand APIs, layers, services, runtime behavior, streams, tools, or devtools
- Verify edge cases or beta-version behavior
- Recommend patterns based on real implementations
When Not to Use
Do not fetch source for:
- Simple setup or installation questions
- Cases where local docs or types already answer the question
- Broad research that does not require implementation details
04 同仓库更多 Skills
belfry-debug
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.
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
turborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in a local file, or native blocking links on a real tracker.
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.