frond

Use when creating, migrating, reviewing, or cleaning up Frond node authoring in this repo, including NodeSpec carriers, NodeBase classes, static specs, Driver.Async/Effect hooks, dependencies, actions, liveness, refresh.

Use when creating commits, pull requests, release PRs, version bumps, npm publish dry-runs, package tarball smoke tests, or release notes for frondruntime.

Use when working with Bun package management, Bun workspaces, bun.lock, package scripts, Bun runtime APIs, Bun build commands, or Node/npm-to-Bun command translation in this repo.

Use before finishing coding work or after deterministic check failures, including lint/typecheck/test loops, interpreting diagnostics as just-in-time prompts, and deciding whether repeated implementation mistakes should become stricter rules.

Use when creating, reviewing, or modifying custom Biome Grit plugins in undefined*.grit, especially deterministic agent-correction rules for stale Effect v3 patterns, local style hazards, and diagnostic messages that tell agents what to do next.

Use when running, interpreting, or modifying Biome linting/formatting/import organization in this repo, including biome.json, Grit plugins, formatting fixes, and lint failures.

Use when creating, modifying, debugging, or running Bun tests with bun:test, including package-local test commands, async tests, mocks, spies, snapshots, and Effect.runPromise test boundaries.

Use after substantial edits, refactors, moves, generated changes, or long sessions to find leftovers, stale stubs, unused imports, accidental compatibility artifacts, and scratch files. Remove only confirmed non-behavioral leftovers; report anything that may affect compatibility or runtime behavior before changing it.

Use when reviewing code changes in Frond, especially to find defects, behavioral regressions, missing tests, weak type modeling, stale compatibility leftovers, and agent-generated implementation artifacts.

Use when working with Effect Fiber, Deferred, Scope, Queue, PubSub, Stream, interruption, background loops, graceful shutdown, backpressure, races, or bounded concurrency in Frond.

Use when modeling Effect errors, defects, Cause handling, Schema contracts, Schema.TaggedErrorClass, boundary decoding/encoding, runtime boundary validation, and typed failure recovery in Frond.

Use when adding or reviewing Effect time, retry, timeout, Clock/Duration, logging, tracing spans, metrics, Config, ConfigProvider, Redacted secrets, or operational observability in Frond.

Use when defining or wiring Effect services in Frond, including Context.Service, service interfaces, Layer.effect/succeed/mergeAll/provideMerge, dependency graphs, runtime construction, and test seams.

Use when testing or verifying Effect code in Frond, including Effect.runPromise boundaries, test layers, fake services, deterministic time, config providers, stream/fiber tests, and runtime edge behavior.

Use when writing, reviewing, or debugging Effect v4 beta code in Frond, especially core Effect composition, Effect.gen, v3-to-v4 API translation, typed Effect signatures, and deciding which narrower Effect skill applies.

Use when reviewing or improving Frond architecture, finding deep refactor candidates, designing runtime/module ownership changes, or deciding whether an Effect-powered runtime concept should be deepened, split, deleted, or documented.

Use when changing Frond package boundaries, splitting or moving modules, shaping public exports, naming APIs, reducing large files, or reviewing repo structure and maintainability.

Use when intentionally restructuring, splitting, renaming, replacing, or reducing complexity in this repo, especially when choosing a clean single path over compatibility, stale aliases, or parallel implementations.

Use when adding, refactoring, reviewing, or debugging tests in Frond, especially package-local test placement, characterization tests, Effect service tests, fixtures, mocks, and deciding how broad verification should be.

Use when writing, refactoring, reviewing, or debugging strict TypeScript in this repo, including tsconfig paths, package exports, typecheck failures, unknown vs any, readonly data, module boundaries, and Effect language-service diagnostics.