Effect-TS

Concise PR finalization changesets. Use when implementation scope is complete and focused validation has finished to classify release impact, consolidate the PR's existing changeset, or write its consumer release note.

Effect development guidance. Use when implementing or reviewing code that composes Effect APIs or patterns, or that adds or changes API signatures.

Pull request finalization. Use when a change works and is about to be opened as a pull request, or when updating or continuing an existing one.

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

Test development. Use when adding or changing Vitest or Tstyche coverage. Choose Tstyche only for intended compiler behavior such as inference, assignability, rejection, or displayed public types.

Find and fix a behavior difference between the Rust port and the Go build - a failing Rust baseline, a failing ported Go test, or a reported Rust-only bug. Use when the Rust baseline runner, a ported test, or a user shows Rust and Go disagree.

Mirror the Go changes of the current branch (vs origin/main) into the Rust port, as the same-PR parity policy requires - find affected markers with `repoctl tsrs port-check`, update the Rust faithfully, fix-lines, ack, run Rust tests and baselines, and…

Orchestrate a round of Rust porting work - pick the Go packages that are ready (all imports ported), hand each to a port-package agent in its own worktree, review and merge the results. The initial port is complete; use this only when a large body of new…

Port one Go package of effect-tsgo (internal/..., etscore, etscheckerhooks, etslshooks, ...) to its Rust crate under crates/, faithfully, with its tests and origin markers, then ack it. Use when asked to port a package, a file range of a package, or the…

Keep the Rust port in step with its upstreams - bump tsrs to a newer commit (rebase _patches/tsrs, regenerate ets_shim, adapt to tsrs API changes), or catch the Rust port up with Go changes that landed without it (a range of commits on main, an upstream…

Polishes and improves the UI in your project. Covers concentric border radius, optical alignment, surface depth, contextual icons, hit areas and more.

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

Audit an existing Foldkit program against the architecture, conventions, and quality bar. Use when the user wants to review their Foldkit code, check for anti-patterns, accessibility gaps, or quality regressions. Triggers on phrases like "audit my app",…

Use whenever working with Foldkit. Triggers on imports from `foldkit`, files in a Foldkit project, or prompts mentioning Foldkit. Loads the framing and points at the `@foldkit` OpenCode reference for canonical conventions, source code, and examples.

Generate a complete, idiomatic Foldkit program from a natural language description. Use when the user wants to create a new Foldkit program, scaffold a project, or says things like "build me a..." or "I want a program that..."

Write, insert, or update Effect public API JSDoc so it satisfies the jsdocs oxlint rule. Use when adding or fixing JSDoc comments, resolving jsdocs diagnostics, preparing docs for JSON extraction, or reviewing public API documentation.

Extract the JSDoc example nearest the active source selection or cursor into ./scratchpad as a TypeScript file. Use when the user asks to dump, copy, open, or try a source example in scratchpad.

Interview the user about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Audit an existing Foldkit program against the architecture, conventions, and quality bar. Use when the user wants to review their Foldkit code, check for anti-patterns, accessibility gaps, or quality regressions. Triggers on phrases like "audit my app",…

Use whenever working with Foldkit. Triggers on imports from `foldkit`, files in a Foldkit project, or prompts mentioning Foldkit. Loads the framing and points at the Foldkit source, fetched into `references/repos/foldkit/`, for the canonical conventions,…

Generate a complete, idiomatic Foldkit program from a natural language description. Use when the user wants to create a new Foldkit program, scaffold a project, or says things like "build me a..." or "I want a program that..."

Audit an existing Foldkit program against the architecture, conventions, and quality bar. Use when the user wants to review their Foldkit code, check for anti-patterns, accessibility gaps, or quality regressions. Triggers on phrases like "audit my app",…

Use whenever working with Foldkit. Triggers on imports from `foldkit`, files in a Foldkit project, or prompts mentioning Foldkit. Loads the framing and points at the canonical Foldkit repository reference, source code, and examples.

Generate a complete, idiomatic Foldkit program from a natural language description. Use when the user wants to create a new Foldkit program, scaffold a project, or says things like "build me a..." or "I want a program that..."

Use for user-visible frontend changes; show desktop and mobile screenshots by default.

Render a web page in a real browser with Cloudflare Browser Run. Use for pages that need JavaScript to show their content, for screenshots or PDFs of a page, or for a page's accessibility tree, when fetchMarkdown returns nothing useful.

Required instructions for filing an issue

Cut AI tells from any writing. Must always apply.

Use this skill when migrating a codebase from Effect v3 to Effect v4, upgrading `effect` or any `@effect/*` package across the v3/v4 boundary.