@danieljvdm/dev-kit 0.18.0 → 1.0.1

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@danieljvdm/dev-kit",
-  "version": "0.18.0",
+  "version": "1.0.1",
   "private": false,
-  "description": "Declarative project development toolkit with portable agent skills.",
+  "description": "Agent-led TypeScript repository setup and curated portable skills.",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -12,59 +12,21 @@
     "dev-kit": "bin/dev-kit.mjs"
   },
   "files": [
-    "dev-kit.example.jsonc",
     "bin/",
-    "schema/",
     "skills/",
     "skill-sources.jsonc",
     "skill-sources.lock.json",
-    "src/",
-    "scripts/",
-    "templates/"
+    "src/"
   ],
   "type": "module",
-  "exports": {
-    ".": {
-      "types": "./src/index.ts",
-      "default": "./src/index.ts"
-    },
-    "./schema": "./schema/dev-kit.schema.json",
-    "./schema/dev-kit.schema.json": "./schema/dev-kit.schema.json",
-    "./schema/skill-sources.schema.json": "./schema/skill-sources.schema.json",
-    "./oxlint": {
-      "types": "./src/oxlint.ts",
-      "default": "./src/oxlint.js"
-    },
-    "./oxfmt": {
-      "types": "./src/oxfmt.ts",
-      "default": "./src/oxfmt.js"
-    },
-    "./vite-plus": {
-      "types": "./src/vite-plus.ts",
-      "default": "./src/vite-plus.js"
-    },
-    "./oxlint-plugin-effect": {
-      "types": "./src/oxlint-plugin-effect.d.ts",
-      "default": "./src/oxlint-plugin-effect.js"
-    },
-    "./oxlint-plugin-anti-slop": {
-      "types": "./src/oxlint-plugin-anti-slop/runtime.d.ts",
-      "default": "./src/oxlint-plugin-anti-slop/runtime.js"
-    },
-    "./oxlint-plugin-style": {
-      "types": "./src/oxlint-plugin-style.d.ts",
-      "default": "./src/oxlint-plugin-style.js"
-    }
-  },
+  "exports": {},
   "scripts": {
-    "prepare": "./bin/dev-kit.mjs apply --locked",
+    "prepare": "./bin/dev-kit.mjs effect sync && ./bin/dev-kit.mjs tsgo patch && vp config --no-agent",
     "dev-kit": "./bin/dev-kit.mjs",
     "changeset": "changeset",
-    "version-packages": "changeset version && ./bin/dev-kit.mjs apply",
+    "version-packages": "changeset version",
     "release": "changeset publish",
     "lint": "vp lint",
-    "plan": "./bin/dev-kit.mjs plan",
-    "apply": "./bin/dev-kit.mjs apply",
     "gitignore": "./bin/dev-kit.mjs gitignore",
     "effect:sync": "./bin/dev-kit.mjs effect sync",
     "test": "vp test",
@@ -77,8 +39,6 @@
   },
   "dependencies": {
     "@effect/platform-bun": "4.0.0-beta.107",
-    "@oxlint/plugins": "1.78.0",
-    "@stylistic/eslint-plugin": "5.10.0",
     "effect": "4.0.0-beta.107",
     "jsonc-parser": "3.3.1",
     "semver": "7.8.5"
@@ -88,6 +48,8 @@
     "@effect/platform-node": "4.0.0-beta.107",
     "@effect/tsgo": "0.36.4",
     "@effect/vitest": "4.0.0-beta.107",
+    "@oxlint/plugins": "1.78.0",
+    "@stylistic/eslint-plugin": "5.10.0",
     "@types/node": "25.9.1",
     "@types/semver": "7.8.0",
     "oxfmt": "0.60.0",
@@ -96,22 +58,6 @@
     "vite-plus": "0.2.6",
     "vitest": "4.1.10"
   },
-  "peerDependencies": {
-    "oxfmt": ">=0.60.0 <0.61.0",
-    "oxlint": ">=1.78.0 <2.0.0",
-    "vite-plus": ">=0.2.6 <0.3.0"
-  },
-  "peerDependenciesMeta": {
-    "oxfmt": {
-      "optional": true
-    },
-    "oxlint": {
-      "optional": true
-    },
-    "vite-plus": {
-      "optional": true
-    }
-  },
   "overrides": {
     "@effect/platform-node-shared": "4.0.0-beta.107"
   },

package/skill-sources.jsonc

@@ -7,6 +7,7 @@
       "ref": "main",
       "skillsPath": "skills",
       "include": [
+        "animate-expo",
         "animation-vocabulary",
         "apple-design",
         "emil-design-eng",

package/skill-sources.lock.json

@@ -5,9 +5,10 @@
       "id": "emilkowalski-skills",
       "repository": "https://github.com/emilkowalski/skills.git",
       "ref": "main",
-      "resolved": "70744e3816f1d93eafb697161a8b880a7384c5ff",
+      "resolved": "e879241fab3cdb22e8d95587cdbf40b57a88d7da",
       "skillsPath": "skills",
       "include": [
+        "animate-expo",
         "animation-vocabulary",
         "apple-design",
         "emil-design-eng",
@@ -18,6 +19,7 @@
         "review-animations"
       ],
       "skills": [
+        "animate-expo",
         "animation-vocabulary",
         "apple-design",
         "emil-design-eng",
@@ -28,6 +30,7 @@
         "review-animations"
       ],
       "descriptions": {
+        "animate-expo": "Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use `animate`.",
         "animation-vocabulary": "Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term (\"the bouncy thing when a popover opens\" → Pop in; \"the iOS rubber-band scroll\" → Rubber-banding). Use when the user asks \"what's it called when…\", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.",
         "apple-design": "Apple's approach to interface design and fluid, physical motion, translated for the web. Use when building or reviewing gesture-driven UI, spring animations, drag/swipe/sheet interactions, momentum and interruptible transitions, translucent materials and depth, typography (optical sizing, tracking, leading), reduced-motion, or the design foundations (feedback, spatial consistency, restraint) behind Apple-style interfaces.",
         "emil-design-eng": "This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.",
@@ -38,6 +41,7 @@
         "review-animations": "Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned."
       },
       "digests": {
+        "animate-expo": "sha256:c9ad6c07908409ed2fa9fecf288196e77325be2cf29e5a03b8aaaecb451709a2",
         "animation-vocabulary": "sha256:d270769a8a19c8ff48489c118e19d5f86113c6acfdd0e981116ffd74b01b9e6b",
         "apple-design": "sha256:dabc421a391bd6b2ba0d004a8f4d4a1b632fc003a45d4676ab9f2ade8099fc7b",
         "emil-design-eng": "sha256:cedac6e0b7ff8ca471d5d2b35dc7d91f13b57ff57c4395822e677f0df7ecebc8",

package/skills/dev-kit/SKILL.md

@@ -1,218 +1,48 @@
 ---
 name: dev-kit
-description: Dev-kit operations for projects that configure dev-kit.jsonc, sync portable skills, run plan/apply or automatic postinstalls, perform locked CI checks, maintain dev-kit.lock.json, resolve ownership conflicts, or enable Effect TypeScript-Go.
+description: Set up or reshape TypeScript repositories through agent-led, repo-owned changes. Use when scaffolding a new repository, establishing or modernizing project tooling, adding an application or package, composing a Cloudflare Worker API, ejecting legacy dev-kit.jsonc and dev-kit.lock.json management, or copying and updating curated agent skills with the transient Dev Kit CLI.
 ---
 
 # Dev Kit
 
-Treat `dev-kit.jsonc` as desired state, `dev-kit.lock.json` as the committed
-resolution, and `.dev-kit/state.json` as local ownership receipts. Deep
-reference — catalog maintenance, package-skill discovery rules, preset
-internals — lives in the package README
-(`node_modules/@danieljvdm/dev-kit/README.md`).
-
-Use the high-level commands for routine changes: `dev-kit init`, `dev-kit add
-<skill...>`, `dev-kit remove <skill...>`, `dev-kit list --all`, `dev-kit search
-<words...>`, and `dev-kit info <skill>`. Add and remove apply immediately unless
-passed `--no-apply`; `dev-kit sync` applies an already-edited manifest.
-
-## Apply loop
-
-1. Establish the Git root. Read project agent instructions, the current
-   manifest and lock, package and workspace manifests, framework and tool
-   configuration, representative source boundaries, and CI workflows. Build a
-   concrete inventory of the platforms, frameworks, tools, and workflows the
-   repository actually uses; do not infer capabilities from a product or
-   company name alone.
-2. Run `dev-kit list --all`, then use `dev-kit search <terms>` and `dev-kit info
-<skill>` for each capability in the inventory. Compare every candidate's
-   trigger description with concrete repository evidence. Keep explicitly
-   requested creative or advisory skills even when they have no mechanical
-   dependency signal.
-3. Choose the narrowest useful set. Prefer focused external skills over a
-   generic umbrella; select an umbrella or source family only when its full
-   breadth is intentionally useful, never because one member matches. Explain
-   any uncertain inclusion before applying it. Unused `references/` folders
-   inside a selected skill cost repository space, not agent context, so a
-   multi-product repository can justify an umbrella while still excluding
-   unrelated top-level skills.
-4. Update `dev-kit.jsonc`. Preserve JSONC comments and validate against the
-   package schema. Finish with each desired resource represented once and every
-   external selection supported by repository evidence or an explicit request.
-5. Run `dev-kit plan`. Use `--manifest`, `--project-dir`, or `--lockfile` when
-   the project overrides their defaults. Planning is read-only; inspect every
-   create, update, remove, adoption, and conflict before proceeding. Finish
-   when the plan contains only intended actions and understood conflicts.
-6. Resolve conflicts, then run `dev-kit apply`. Commit the manifest and
-   regenerated `dev-kit.lock.json`; keep `.dev-kit/` local. Finish when a second
-   plan reports only unchanged resources and setup tasks.
-
-## Manifest
-
-Use skill names or family names in `include`; subtract selections with
-`exclude`. Built-in families such as `effect` are intentional bundles. Include
-this skill as `dev-kit` when project agents should carry the toolkit
-procedure. Skills bundled inside installed packages need the exact
-`<package>#<skill>` selector; the copied output flattens that identity into
-one directory name (`@tanstack/table-core#core` → `tanstack-table-core-core`)
-and rewrites the copied frontmatter `name:` to match.
-
-```jsonc
-{
-  "$schema": "./node_modules/@danieljvdm/dev-kit/schema/dev-kit.schema.json",
-  "include": ["dev-kit", "effect"],
-  "setup": {
-    "agentInstructions": { "enabled": true },
-    "claudeInstructions": { "enabled": true },
-    "vitePlus": {
-      "hooks": { "enabled": true },
-      "workflow": { "enabled": true },
-    },
-    "worktrunk": {
-      "config": { "enabled": true },
-    },
-  },
-  "targets": {
-    "agents": { "enabled": true, "mode": "copy" },
-    "claude": { "enabled": true, "mode": "symlink" },
-  },
-}
-```
-
-Prefer a copied `.agents/skills` target as the project-local source of truth;
-use symlinks for additional harness discovery paths. Keep every target path
-project-relative and separate from the manifest, lock, and state paths.
-
-## Managed instructions
-
-`setup.agentInstructions` manages marked sections in the project-root
-`AGENTS.md` and preserves handwritten content around them; edit only outside
-the markers. The section points agents at this skill, renders the repository's
-command policy from live evidence (a direct `vite-plus` dependency makes `vp`
-the only front door; otherwise Bun runs declared root scripts), and adds the
-Effect guide pointer when the installed `effect` package ships one. Treat
-duplicate, overlapping, reversed, or unmatched managed markers as a conflict
-rather than guessing which content Dev Kit owns. Never substitute another
-script runner or call raw `tsc`, test, lint, or format binaries when a project
-command exists.
-
-`setup.claudeInstructions` manages `CLAUDE.md` as a relative symlink to
-`AGENTS.md`. Disabling either task removes only unchanged managed content and
-leaves handwritten content in place.
-
-## Vite+ setup
-
-The repository always owns `vite.config.ts`. Compose
-`createRecommendedVitePlusConfig` from `@danieljvdm/dev-kit/vite-plus` there,
-adding repository/framework-generated paths (and any overridden harness target
-paths) through `ignorePatterns`. Spread the returned top-level config before
-local options, spread a returned nested block before overriding it, and merge
-nested collections such as `lint.rules` so the recommended rules stay active.
-The factory provides matching Oxlint/Oxfmt ignores, staged checks, and
-separate `check` and pure `typecheck` tasks; standalone Oxc projects import
-`recommendedOxlintConfig`/`recommendedOxfmtConfig` directly.
-
-Run the Effect-patched compiler separately with `vp run typecheck`; neither
-Oxlint's bundled `tsgolint` nor Vite+'s native lint path uses the Effect patch.
-Keep Oxlint and `@oxlint/plugins` on the matching version expected by the
-preset so Vite+ can execute its JavaScript plugins. The `effect` plugin's
-scope-sensitive rules stay consumer-scoped: enable them per path in
-Effect-owned code, with exceptions for tests and host boundaries.
-
-`setup.vitePlus.hooks` converges the Git-ignored `.vite-hooks/_` dispatcher by
-running the project-local `vp config --no-agent`, recreating it in linked
-worktrees. It requires a direct `vite-plus` dependency, refuses to replace an
-unrelated `core.hooksPath`, and is skipped per invocation with
-`VITE_GIT_HOOKS=0` or `HUSKY=0`.
-
-## Scaffolds
-
-`setup.vitePlus.workflow` and `setup.worktrunk.config` are create-only
-scaffolds: apply writes the file only when it is missing, records nothing in
-the lock, and never reads, updates, or removes an existing file — the
-repository owns it from creation and edits it directly. When the shipped
-template improves, diff the repository's file against the installed template
-under `node_modules/@danieljvdm/dev-kit/templates/` and merge what fits.
-
-- `setup.vitePlus.workflow` scaffolds `.github/workflows/check.yml`. It
-  requires direct Dev Kit, compatible Vite+, Effect, Effect TypeScript-Go, and
-  native TypeScript dependencies with `setup.effectTsgo.enabled`. Add
-  preparation steps or a custom typecheck command by editing the YAML.
-- `setup.worktrunk.config` scaffolds `.config/wt.toml`: a
-  copy-ignored-then-install pre-start pipeline, a full-validation pre-merge
-  hook, and a commented per-worktree dev-server block to enable deliberately.
-  Hook commands render for the repository's runner — `vp` with a direct
-  `vite-plus` dependency, otherwise the detected package manager's install
-  command with `bun run check` from a declared root `check` script. Keep
-  user-level Worktrunk settings such as worktree-path templates out of the
-  project config; each user approves the hooks once with
-  `wt config approvals add`.
-
-## Ownership and conflicts
-
-Dev-kit adopts an existing destination only when its digest exactly matches a
-committed lock entry. Local receipts authorize later updates and cleanup only
-while the managed output still matches its recorded digest.
-
-Preserve a conflicting path and inspect it:
-
-- For an unknown destination, choose a different target or deliberately move
-  the user-owned content before applying.
-- For a modified managed destination, reconcile the local edits or restore its
-  recorded content before applying.
-- For a locked-plan mismatch, run an unlocked apply only when intentionally
-  updating desired state, review the new lock, and commit it.
-
-Retain `.dev-kit/state.json` across routine applies and branch changes so its
-receipts can update or remove previously applied outputs safely.
-
-## Lifecycle
-
-Run `dev-kit gitignore` to add `.repos/` and `.dev-kit/` additively
-(`--dry-run` to preview). For one lifecycle entry point, configure:
-
-```jsonc
-{
-  "scripts": {
-    "postinstall": "dev-kit apply",
-  },
-}
-```
-
-This intentionally refreshes the committed lock and owned outputs when an
-installed Dev Kit or selected package-skill version changes; review and commit
-those changes with the dependency update. Keep `dev-kit apply --locked` as a
-verification command, never the local lifecycle, and never run an unlocked
-apply before locked verification. Invoke locked consumer verification as
-`bun ./node_modules/@danieljvdm/dev-kit/bin/dev-kit.mjs apply --locked` so a
-package script named `dev-kit` cannot shadow the executable.
-
-## Effect setup tasks
-
-`setup.effectSource` converges the ignored `.repos/effect` checkout on the
-`effect@<version>` tag matching the installed package. It skips CI, preserves
-a dirty or unrelated destination, and never deletes the checkout when
-disabled. Diagnose with `dev-kit effect sync --dry-run`; override
-`packageName`, `path`, or `repository` only for a compatible Effect
-distribution.
-
-`setup.effectTsgo` validates and patches the project-local native TypeScript
-compiler. Install the exact `@effect/tsgo` and `typescript` versions required
-by the installed dev-kit, point `tsconfig.json` at
-`./node_modules/@effect/tsgo/schema.json`, and configure the
-`@effect/language-service` plugin with the `recommendedEffectTsgoPlugin`
-profile — copy the exact JSON from the package README. In monorepos, child
-`compilerOptions.plugins` arrays replace rather than merge the root array, so
-workspace configs must inherit the root plugin without redeclaring it, and the
-`src/**/*.ts` override must be relative to the config that contains it.
-Diagnose with `dev-kit tsgo patch --dry-run`; use `--force` only after the
-user accepts a potentially commit-incompatible TypeScript binary.
-
-## Current boundary
-
-Manage skill outputs, the `setup.agentInstructions` marked sections, the
-`setup.claudeInstructions` link, the `setup.vitePlus.hooks` dispatcher, the
-`setup.effectSource` checkout, and the explicit `setup.effectTsgo` task. The
-`setup.vitePlus.workflow` and `setup.worktrunk.config` scaffolds belong to the
-repository once created. `vite.config.ts`, dependency, and `tsconfig.json`
-contributions remain deliberate user-owned edits.
+Build repositories from intent, then leave every output under normal repository
+ownership. Use the transient CLI for catalog and migration mechanics; use agent
+judgment for architecture and configuration.
+
+## Route
+
+Read every reference whose branch applies before editing:
+
+- Read [repository-setup.md](references/repository-setup.md) for every new,
+  existing, or expanded repository.
+- Read [default-typescript-repository.md](references/default-typescript-repository.md)
+  when the user wants the Dev Kit default or a Vite+ TypeScript foundation.
+- Read [cloudflare-worker-api.md](references/cloudflare-worker-api.md) when adding
+  a Cloudflare Worker, Worker API, bindings, Durable Objects, or Wrangler.
+- Read [legacy-eject.md](references/legacy-eject.md) when `dev-kit.jsonc`,
+  `dev-kit.lock.json`, `.dev-kit/state.json`, managed markers, or Dev Kit config
+  imports exist.
+- Read [skills.md](references/skills.md) when discovering, adding, refreshing,
+  merging, or detaching repository skills.
+
+## Workflow
+
+1. Establish the Git root and read repository instructions. Inventory package
+   manifests, workspaces, tool configuration, source boundaries, CI, and current
+   validation commands. Finish with every existing convention that constrains
+   the change accounted for.
+2. Translate the request into outcomes and invariants. Resolve consequential
+   choices with the user; infer naming and file placement from repository
+   evidence. Finish with a coherent target architecture rather than a list of
+   templates.
+3. Present the material file, dependency, and command changes before broad or
+   destructive work. Treat existing files as repository-owned and reconcile
+   them in place.
+4. Implement against current installed APIs and local documentation. When the
+   repository uses Effect, read `node_modules/effect/AGENTS.md` completely before
+   writing Effect code and follow its relevant references.
+5. Run the repository's command authority and exercise the changed behavior.
+   Finish when validation passes and the generated setup works from the same
+   entry points future contributors will use.
+6. Hand off the architecture and any deliberate choices. The finished repository
+   has no Dev Kit dependency, manifest, lock, lifecycle hook, or managed output.

package/skills/dev-kit/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "Dev Kit"
-  short_description: "Configure and apply portable project tooling"
-  default_prompt: "Use $dev-kit to configure and safely apply this project's development toolkit."
+  short_description: "Build an agent-ready TypeScript repository"
+  default_prompt: "Use $dev-kit to set up this repository from my requirements and leave every result repo-owned."

package/skills/dev-kit/references/cloudflare-worker-api.md

@@ -0,0 +1,37 @@
+# Cloudflare Worker API
+
+Use the `build-effect-apis`, `workers-best-practices`, and `wrangler` skills when
+they are available. Read current installed or primary Cloudflare documentation
+before choosing Wrangler configuration, compatibility dates, bindings, or local
+development commands.
+
+## Boundary
+
+Model the Worker as a deployable package with an explicit host boundary. Keep
+contracts and application services independent of Worker globals. Translate
+bindings, requests, execution context, and platform failures at the entry point,
+then assemble the application layer once.
+
+When the repository uses Effect, define shared HTTP contracts before handlers,
+keep failures typed through the application, and connect the final handler to
+the Worker adapter. Generate clients or OpenAPI from the same contract when the
+product needs them.
+
+## Configuration
+
+Derive binding types from Wrangler configuration and include the generated file
+in the package's typecheck without hand-maintained ambient duplicates. Separate
+secret names from secret values. Scope environment-specific resources in
+Wrangler rather than branching through application code.
+
+Integrate Worker development, type generation, deployment, and dry-run commands
+into the repository's existing command authority. Add the narrow Cloudflare
+skills that match the selected products; a Worker alone does not justify every
+Cloudflare skill.
+
+## Completion
+
+Generate bindings, run repository validation, build or dry-run the Worker, and
+exercise one request through the actual Worker entry point. Account for streaming,
+request cancellation, background work, observability, and binding failures before
+declaring the API ready.

package/skills/dev-kit/references/default-typescript-repository.md

@@ -0,0 +1,43 @@
+# Default TypeScript repository
+
+Use this branch when the user requests the Dev Kit default or chooses Vite+ as
+the repository toolchain. Adapt package boundaries to the requested product;
+the defaults below are invariants, not a fixed directory template.
+
+## Foundation
+
+- Use Bun as the package manager and declare its version through `packageManager`.
+- Use Vite+ as the command authority for install, format, lint, tests, typecheck,
+  builds, and repository tasks. Read its installed documentation before choosing
+  config keys or commands.
+- Keep `vite.config.ts`, TypeScript configs, lint plugins, ignore patterns, and
+  task composition local and repository-owned.
+- Give formatting, linting, tests, and pure typechecking distinct commands, then
+  compose them into one full validation task.
+- Make CI invoke the same repository commands developers use.
+- Keep generated files and vendored source in explicit tool ignores.
+
+## TypeScript
+
+Build a root configuration around the repository's actual runtime targets and
+workspace graph. Let child packages inherit shared strictness while declaring
+only their environment-specific libraries, paths, and emitted output. Keep
+compiler plugins at the configuration level where their file globs are correct.
+
+When Effect TypeScript-Go is selected, install its commit-matched compiler and
+language service according to the installed Effect guidance. Materialize any
+required patch helper into a repository-owned script so installs never depend on
+Dev Kit.
+
+## Workspaces
+
+Create a package only for a real deployable, reusable boundary, or independently
+validated unit. Give every package a narrow public surface and a pure typecheck
+task. Configure the root validation task to cover every workspace without hiding
+package failures behind a root-only compiler invocation.
+
+## Completion
+
+Run the full Vite+ validation and at least one real build or startup path. The
+result must contain no import from `@danieljvdm/dev-kit` and no command that needs
+the Dev Kit executable after setup.

package/skills/dev-kit/references/legacy-eject.md

@@ -0,0 +1,46 @@
+# Legacy ejection
+
+Treat ejection as a migration of ongoing behavior, followed by deterministic
+release of Dev Kit ownership.
+
+## Inventory
+
+Read `dev-kit.jsonc`, `dev-kit.lock.json`, `.dev-kit/state.json` when present,
+`package.json`, agent instructions, CI, Vite+/Oxlint/Oxfmt configuration, Git
+hooks, Effect setup, and every `@danieljvdm/dev-kit` import or executable call.
+Run:
+
+```bash
+bunx @danieljvdm/dev-kit@latest eject --dry-run
+```
+
+Finish the inventory with every managed skill, modified managed output, runtime
+config import, lifecycle command, and enabled setup task accounted for.
+
+## Materialize
+
+Replace Dev Kit config imports with local repository-owned configuration. Copy
+small custom plugins or helpers locally; keep a focused package dependency only
+when the repository intentionally consumes that package at runtime.
+
+Translate recurring setup tasks into repository-owned mechanisms before removing
+the dependency. Effect compiler patching, source checkouts, Git hook generation,
+and CI preparation must continue to work after a fresh clone and install.
+
+Preserve agent instructions while removing the managed wrapper and obsolete
+claims that Dev Kit owns the repository. Preserve local skill edits. The eject
+command converts safe legacy skill outputs into tracked repo-owned skills and
+adds origin receipts for optional future updates.
+
+## Release ownership
+
+Resolve every conflict reported by dry-run, then run:
+
+```bash
+bunx @danieljvdm/dev-kit@latest eject
+```
+
+Inspect the diff and run a fresh install plus the full repository validation.
+Search again for Dev Kit imports, lifecycle calls, the manifest, the lock, and
+managed markers. Finish when Dev Kit is absent from dependency resolution and
+the repository retains all intended behavior.

package/skills/dev-kit/references/repository-setup.md

@@ -0,0 +1,53 @@
+# Repository setup
+
+## Inspect
+
+Classify the work as an empty repository, an established repository, or a new
+package inside an established workspace. Read the files that reveal:
+
+- package manager and workspace topology;
+- runtime and deployment targets;
+- TypeScript inheritance and module boundaries;
+- formatting, linting, typechecking, tests, builds, and Git hooks;
+- CI and release expectations;
+- existing agent instructions and skills.
+
+For an empty repository, establish Git and package metadata first, install the
+chosen toolchain, then read documentation shipped by those dependencies before
+writing framework-specific source.
+
+## Model
+
+Turn requested capabilities into one repository model. Let features contribute
+requirements, while shared configuration receives one coherent implementation.
+For example, Worker bindings, Effect compiler settings, generated source ignores,
+and workspace typechecking should converge in the same TypeScript and Vite+
+design instead of being patched by isolated recipes.
+
+Keep architectural choices proportional to evidence. Ask about product or
+deployment decisions that change package boundaries. Derive routine names,
+paths, and scripts from nearby conventions.
+
+## Apply
+
+Write ordinary project files without generated ownership markers. Prefer local,
+readable configuration over a persistent preset dependency. Add focused runtime
+or tooling dependencies only when the repository actually executes their code.
+
+For an established repository, preserve working conventions and integrate the
+requested capability at their natural seams. For an empty repository, create
+the smallest runnable vertical slice before filling out auxiliary tooling.
+
+Generate agent instructions from live project evidence. Record command authority,
+Effect documentation routing when applicable, and non-obvious boundaries; leave
+discoverable script names and directory listings to the repository itself.
+
+## Verify
+
+Install through the selected package manager, run the repository's full command
+authority, and exercise a runtime or build entry point for each new application.
+Inspect the final diff for placeholder text, unused dependencies, stale generated
+paths, accidental Dev Kit imports, and configuration that only works in the
+creating worktree.
+
+Finish with a repository that can be cloned and operated without Dev Kit.

package/skills/dev-kit/references/skills.md

@@ -0,0 +1,35 @@
+# Repository skills
+
+The transient CLI copies skills directly into `.agents/skills`. Each copied
+skill is repository-owned. A `.dev-kit-origin.json` file inside that skill records
+only its selector, approved source, and base digest; it is not desired state and
+runs no lifecycle.
+
+## Discover and add
+
+Inspect repository capabilities before selecting skills. Search descriptions and
+prefer the narrowest matching skills:
+
+```bash
+bunx @danieljvdm/dev-kit@latest skills search cloudflare
+bunx @danieljvdm/dev-kit@latest skills info workers-best-practices
+bunx @danieljvdm/dev-kit@latest skills add workers-best-practices wrangler
+```
+
+Treat source families as broad selections: add one only when every member applies.
+
+## Refresh
+
+Run `skills status` before updates. `skills update` fast-forwards a skill only
+when its repository copy still matches the recorded base. For a locally modified
+skill whose upstream also changed, inspect `skills diff`, merge the relevant
+upstream intent into the repository copy, and preserve local policy deliberately.
+
+After a manual merge, preserve the merged content and advance its base with
+`skills update <name> --accept-local`. A future CLI may automate three-way
+merges; current conflicts remain agent-owned rather than being overwritten.
+
+## Detach
+
+Run `skills detach <name>` to remove only the origin receipt. The skill content
+stays in place as an ordinary local skill and future Dev Kit updates ignore it.