effect-ts/effect · Archived

jsdocs

Public API JSDoc. Use when authoring or reviewing Effect API documentation, refining a module's documentation, or fixing documentation related diagnostics.

First seen Aug 1, 2026

Installation

$ npx skills add effect-ts/effect --skill jsdocs

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from effect-ts/effect · top by installs.

npx skills add effect-ts/effect

Browse all from effect-ts/effect

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 15.9K
License LICENSE
Default branch main
Open issues 167
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,777 B
  • docs SUMMARY.md 169 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Workflow

  1. Inspect the declaration, implementation, nearby JSDoc, tests, and call sites.
  2. Select every applicable branch and load its reference before editing:

- tags, modules, or links: [declarations.md](declarations.md); - categories: [categories.md](categories.md); - examples: [examples.md](examples.md).

  1. Make a focused API fix or module refinement. Preserve verified facts and

valuable examples rather than rewriting mechanically.

  1. For module refinement or APIs with close alternatives, audit @see links

and inspect implementation and tests for concrete Gotchas.

  1. Run pnpm jsdocs --check and every applicable root validation command.

@internal declarations and default exports are outside public JSDoc authoring. Checked files do not support exported enums or empty export declarations.

Public declarations use a multiline block with one self-contained practical description paragraph. Start functions and methods with a present-tense action; match nearby noun-family phrasing for values. Optional non-empty sections appear once in this order: When to use, Details, Gotchas. Separate descriptions, sections, examples, and tags with one blank line. When to use states a positive use case distinct from the description; reserve Gotchas for concrete caveats and failure modes.

The task is complete when every changed public declaration satisfies each applicable reference, the checker passes, runnable examples pass their targeted doctest, and all other applicable root checks pass or are reported as not run.