effect-module-resource
Guidance for `effect/Resource` focused on APIs like get, isResource, and auto. Load after `effect-skill-router` when this module is the primary owner.
Best use case
effect-module-resource is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Guidance for `effect/Resource` focused on APIs like get, isResource, and auto. Load after `effect-skill-router` when this module is the primary owner.
Teams using effect-module-resource should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/effect-module-resource/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How effect-module-resource Compares
| Feature / Agent | effect-module-resource | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Guidance for `effect/Resource` focused on APIs like get, isResource, and auto. Load after `effect-skill-router` when this module is the primary owner.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Effect Module Resource
## Owned scope
- Owns only `effect/Resource`.
- Source of truth: `packages/effect/src/Resource.ts`.
## What it is for
- Module-specific APIs and usage patterns for Effect programs.
## API quick reference
- `get`
- `isResource`
- `auto`
- `manual`
- `refresh`
- `Resource`
- Full API list: `references/api-reference.md`
## How to use it
- Treat stateful APIs as synchronization boundaries and keep updates atomic.
- Use the reference docs to select the smallest API surface that solves your task.
- Validate behavior against existing tests before introducing new usage patterns.
## Starter example
```ts
import { Resource } from "effect/Resource";
const value = Resource.get();
```
## Common pitfalls
- Prefer explicit, typed combinators over ad-hoc casting or unchecked assumptions.
## Not covered here
- Adjacent modules in `effect/*` and `effect/unstable/*` are out of scope for this owner.
## Escalate to
- `effect-skill-router` for routing and ownership checks.
## Reference anchors
- Module source: `packages/effect/src/Resource.ts`
- Representative tests: `packages/effect/test/Resource.test.ts`
- API details: `references/api-reference.md`
- Usage notes: `references/usage-reference.md`
- Ownership mapping: `references/owner.md`Related Skills
logging-module-usage
Employs the logging module judiciously to log important events, warnings, and errors.
Facets Modules Validate
Validate changed Facets modules: lint against all rules defined in rules.md AND run raptor dry-run. Auto-detects changed modules from git diff.
effect-module-request
Guidance for `effect/Request` focused on APIs like of, fail, and succeed. Load after `effect-skill-router` when this module is the primary owner.
effect-layers-services
Define services, provide layers, compose dependencies, and switch live/test. Use for DI boundaries and app composition.
dataverse-python-modules
dataverse-python-modules guidelines Triggers on: **
aposd-reviewing-module-design
Evaluate module design using APOSD principles with 40-item checklist. Detect complexity symptoms (change amplification, cognitive load, unknown unknowns), shallow modules, information leakage, pass-through methods, and structural anti-patterns. Produce categorized design review (Critical/Moderate/Observations/Positive). Use when reviewing code, assessing interfaces, during PR review, or evaluating 'is this too complex?' Triggers on: code review, design review, module complexity, interface assessment, PR review, structural analysis.
aposd-designing-deep-modules
Enforce Design-It-Twice workflow: generate 2-3 radically different approaches, compare them, then implement. Use when designing modules, APIs, or classes before implementation. Triggers on: design, create class, add module, implement feature, new service, API design, before implementing. Produces structured design document with approaches, comparison table, choice rationale, and depth check.
analyze-m1-module-for-migration
Systematically analyze a Magento 1 module to determine its purpose, usage, and migration requirements for Magento 2. Use when you need to decide whether to migrate a M1 module, find alternatives, or skip it.
amplifier-modulebuilder-skill
Build amplifier-foundation modules using "bricks and studs" architecture. Covers tool, hook, provider, context, and orchestrator modules with testing, publishing, and best practices.
add-module
Create a new core infrastructure module with standard API, lazy init, and proper structure
1k-patching-native-modules
Patches native modules (expo-image, react-native, etc.) to fix native crashes or bugs.
aesthetic-usability-effect
Los diseños atractivos se perciben como más usables. Use cuando justifique inversión en diseño visual, diseñe primeras impresiones, o maneje errores.