v2.0.2

Patch Changes

• 6f1a001: Upgrade the Effect TypeScript-Go compiler baseline to 0.45.0 and enable typed Schema decoder and focused Effect simplification warnings in the recommended TypeScript setup.
  Pin the compatible platform runtime so fresh CLI installs keep a consistent Effect version.

v2.0.1

Patch Changes

• 1789a5e: Refine the pull request skill to focus on the final change, omit routine test and validation reporting, and use before/after visual and performance comparisons where useful.

v2.0.0

Major Changes

• 4e4ea48: Consolidate owned skills into eight task entrypoints with conditional references.
  Replace retired selectors explicitly when adopting this release:

  • animate: motion improvement, review, opportunities, and animation vocabulary.
  • design-ui: Apple/design-engineering guidance, prototypes, and UI library selection.
  • cloudflare-workers: Worker practices, Durable Objects, Wrangler, and Sandbox SDK.
  • effect-development: Effect setup, architecture, HTTP APIs, CLIs, and Atom state.
  • sentry: all eight Sentry workflows, sharing platform and signal references.
  • testing: test selection and explicitly requested TDD.

  dev-kit and open-pull-request remain separate task entrypoints. The effect
  family now selects effect-development. Existing consumer files are repo-owned;
  install the replacements, preserve local guidance, and remove retired copies
  when adopting. Old individual selectors are no longer in the catalog.

  Use Effect Atom for shared React state, choose theme handling from the existing
  SSR and persistence setup, preserve user scope, and follow repository testing
  policy. Retain upstream licenses and pinned provenance for maintained forks.

v1.0.2

Patch Changes

• fd2729b: Add HumanLayer's show-me to the approved skill catalog and update the pull request skill to favor brief summaries, focused architecture diagrams, and concrete API examples.

v1.0.1

Patch Changes

• 320cffd: Refresh Emil Kowalski's approved skill catalog and add animate-expo for building polished animations and gestures in Expo apps.

v1.0.0

Major Changes

• 0caa455: Replace persistent project reconciliation with agent-led, repo-owned setup. Add
  manifestless skill installation and provenance-aware updates, ship a conservative
  eject migration for v1 managed projects, and remove the manifest manager and
  importable configuration API from the published package.

v0.18.0

Minor Changes

• f953091: Vendor anti-slop, export its Oxlint plugin, and enable its low-evidence rules in the recommended lint preset.

Patch Changes

• 946ef3b: Update the Effect v4 beta family to beta.107 and Effect TypeScript-Go to 0.36.4 while preserving its commit-matched TypeScript 7.0.2 compiler.

v0.17.0

Minor Changes

• 96a7d40: Approve Sentry's official agent skills from getsentry/agent-plugin in the external skill catalog.

v0.16.0

Minor Changes

• 253086d: Add opt-in absolute (path-alias) import enforcement: createRecommendedVitePlusConfig({ absoluteImports: { files } }) appends an Oxlint override scoping import/no-relative-parent-imports to the given globs, and createAbsoluteImportsOxlintOverride exposes the same override for standalone Oxlint configs.

• 45ff273: Share skill-source and Effect-source downloads through a machine-global cache.

  Catalog source checkouts now materialize into $XDG_CACHE_HOME/dev-kit
  (~/Library/Caches/dev-kit on macOS, ~/.cache/dev-kit elsewhere, overridable
  with DEV_KIT_CACHE_DIR) keyed by source id and resolved commit SHA, instead
  of the per-project .dev-kit/cache. A fresh git worktree with the same pinned
  sources applies without any network access, and dev-kit plan no longer
  re-fetches catalog sources on every run — the dry-run path reads and populates
  the same cache. Cache population stages into a temp sibling and renames
  atomically, so concurrent applies from different worktrees are safe. Because
  entries are immutable and commit-keyed, populating the cache is not project
  state; planning and --locked verification use it without violating their
  read-only project semantics.

  The setup.effectSource checkout keeps its per-project .repos/effect
  working copy but clones and fetches tags from a shared cached repository in
  the same global cache, contacting the network only when a tag is missing from
  the cache.

  The cache does not grow without bounds. Every use refreshes a recency stamp;
  dev-kit apply sweeps content unused for 30 days at most once a day, dropping
  stale catalog entries and unused Effect tags (removing a shared repository
  entirely once it holds no tags). The new dev-kit cache prune command sweeps
  on demand, with --max-age-days to tune the threshold and --all to clear
  the cache entirely. Eviction is always safe: entries are regenerable and are
  re-fetched on next use.

  Stale project-local .dev-kit/cache/catalog directories left by earlier
  versions are removed on apply (best effort); they were regenerable and are no
  longer read.

• 129e052: Split the consumer half of build-effect-apis into a new effect-atom-state skill so client-side work actually triggers it.

  • New effect-atom-state skill owns Effect Atom client state and React integration: deriving AtomHttpApi/HttpApiClient clients, query/mutation atoms, reactivity keys, Atom.fn workflows, optimistic updates, lifecycle, testing, and TanStack Start. Its description triggers on writing or refactoring React components that read or dispatch atoms — the case the old server-flavored description never matched. The skill body carries the Effect→Promise boundary doctrine: business logic stays in Effect, promise-mode dispatches are returned bare to promise-shaped leaf components, multi-step workflows compose atoms through the fn context, cross-query invalidation is declared as reactivity keys, and optimistic state lives in Atom.family atoms.
  • build-effect-apis keeps the contract spine and server: shared contracts, handlers and middleware, runtime assembly, Cloudflare Workers, and verification. It routes consumer changes to $effect-atom-state. The effect family now installs both.
  • setup.agentInstructions renders a terse Effect Atom client boundary section into the managed AGENTS.md when the project (or one of its workspace packages) depends on @effect/atom-react.

v0.15.0

Minor Changes

• 60cb47a: Introduce create-only scaffolds: setup tasks that apply a template once and then leave the file to the repository — never locked, compared, updated, or removed.

  • New setup.worktrunk.config scaffolds a default Worktrunk project config at .config/wt.toml: a copy-ignored-then-install pre-start pipeline, a full-validation pre-merge hook, and a commented per-worktree dev-server post-start block. Hook commands render for the repository's command runner — vp install and vp run check with a direct vite-plus dependency, otherwise the detected package manager's install command with bun run check from a declared root check script.
  • Breaking: the managed GitHub Actions check workflow became a scaffold. The manifest key moved from setup.vitePlus.quality.workflow to setup.vitePlus.workflow, and the beforeChecks and typecheck options were removed — edit the scaffolded YAML directly instead. On upgrade, existing setup:vite-plus-github-actions lock entries and receipts are discarded and .github/workflows/check.yml becomes repository-owned; re-apply any beforeChecks/typecheck customization by editing the file.
  • Breaking: removed the raw-file-mode digest fallback that adopted locks written by dev-kit ≤0.6. If a locked verification fails after upgrading from those versions, run one unlocked dev-kit apply and commit the regenerated lock.