@icebreakers/monorepo-templates 1.3.4 → 2.0.0

package/assets/.agents/skills/repoctl/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: repoctl
+description: Create and maintain pnpm/Turborepo workspaces with repoctl. Use when the user says 使用 repoctl 创建项目, create a monorepo, pnpm create repoctl, scaffold Vue/Hono/tsdown/vitepress, or run repo init/doctor/new/check.
+---
+
+# repoctl
+
+The package name is `repoctl`. The command is `repo`.
+
+## Empty directory
+
+Do not prompt. Map the request to template keys, then:
+
+```bash
+pnpm create repoctl <dir> -- --yes --templates <keys>
+cd <dir>
+pnpm install
+pnpm exec repo init
+pnpm exec repo doctor
+```
+
+`npm create` and `pnpm create` need the extra `--` before flags. `npx create-repoctl <dir> --yes --templates <keys>` does not.
+
+| User intent              | `--templates` key  |
+| ------------------------ | ------------------ |
+| Vue / full-stack web app | `vue-hono`         |
+| API / Hono service       | `hono-server`      |
+| TypeScript library / SDK | `tsdown`           |
+| Vue component library    | `vue-lib`          |
+| Documentation site       | `vitepress`        |
+| CLI                      | `cli`              |
+| Unspecified              | omit `--templates` |
+
+Then implement the requested feature in the generated workspace.
+
+## Existing repoctl workspace
+
+Look for `pnpm-workspace.yaml` and a `repoctl` / `repo` dependency.
+
+```bash
+pnpm exec repo templates
+pnpm exec repo new <name> --template <key>
+pnpm exec repo check
+```
+
+## Verify
+
+```bash
+pnpm exec repo doctor
+pnpm exec repo check
+```
+
+## Do not
+
+- Do not add packages by copying folders.
+- Do not hang on create prompts; pass `--yes`.
+- Do not create business apps inside the `sonofmagic/repoctl` source repository.
+
+## References
+
+- `references/templates.md` for template keys and `repo new` flags.
+- `references/commands.md` for other CLI commands.
+- `references/config.md` for `repoctl.config.ts`.

package/assets/.agents/skills/repoctl/references/commands.md

@@ -0,0 +1,243 @@
+# Commands
+
+## init
+
+Purpose: bootstrap workspace metadata plus recommended tooling defaults.
+Usage:
+
+- pnpm exec repo init
+  Options:
+- --preset <minimal|standard>: choose a lighter or fuller setup
+- --force: overwrite existing tooling config files
+  Notes:
+- `standard` is the default preset
+- `minimal` currently focuses on the base TypeScript setup
+
+## new
+
+Purpose: create a new package or app through an intent-driven flow.
+Usage:
+
+- npx repoctl new
+- npx repoctl new my-lib
+  Notes:
+- Prompts for what you want to create first, then maps to a template
+- `library` defaults to `packages/<name>`
+- `web-app`, `api-service`, `docs-site`, and `cli-tool` default to `apps/<name>`
+- Advanced users can still use `repoctl package create` or `repoctl pkg new`
+
+## check
+
+Purpose: run recommended local checks.
+Usage:
+
+- npx repoctl check
+- npx repoctl check --staged
+- npx repoctl check --full
+- npx repoctl check --dry-run
+- npx repoctl check --json --out reports/check-plan.json
+  Notes:
+- default mode runs the lightweight local verification flow
+- `--staged` adds staged typecheck routing
+- `--full` maps to the heavier pre-push verification flow
+- `--dry-run` previews the verification route without running checks
+- `--json` and `--out <file>` emit the same plan for automation and imply dry-run
+
+## doctor
+
+Purpose: diagnose whether the current workspace is ready to use.
+Usage:
+
+- npx repoctl doctor
+- npx repoctl doctor --json
+- npx repoctl doctor --json --out reports/doctor.json
+  Notes:
+- default output is human-readable
+- `--json` emits the structured report only and still exits non-zero when blocking failures exist
+- `--out <file>` persists the text or JSON report and still exits non-zero when blocking failures exist
+
+## upgrade
+
+Purpose: sync repo assets and scripts into the workspace.
+Usage:
+
+- npx repoctl upgrade
+- npx repoctl workspace upgrade
+- npx repoctl ws up
+  Options:
+- --interactive: prompt for overwrites
+- --core: sync core config only (skip GitHub assets)
+- --outDir <dir>: write to another directory
+- --skip-overwrite: never overwrite existing files
+- --overwrite-release: explicitly replace an unmarked custom release workflow
+
+For the first migration of an existing project, bootstrap with
+`pnpm dlx repoctl@latest upgrade --yes`. Managed and official legacy release
+workflows are migrated automatically; unmarked custom workflows are preserved
+unless `--overwrite-release` is supplied.
+
+## release ci
+
+Purpose: provide the single GitHub Actions entrypoint for stable and prerelease orchestration.
+Usage:
+
+- `pnpm exec repo release ci`
+- `pnpm exec repo release ci --mode prepare`
+- `pnpm exec repo release ci --mode publish`
+- `pnpm exec repo release ci --mode publish-unpublished --package <name> --version <version>`
+
+The command uses `GITHUB_TOKEN`, `GITHUB_REPOSITORY`, `GITHUB_API_URL`, and
+`GITHUB_SHA` to upsert the Release PR, package tags, and GitHub Releases. It
+consumes `pnpm-publish-summary.json` and is safe to retry.
+
+## workspace upgrade (alias: ws up)
+
+Purpose: sync monorepo assets and scripts into the workspace.
+Usage:
+
+- npx repoctl workspace upgrade
+- npx repoctl ws up
+  Options:
+- --interactive: prompt for overwrites
+- --core: sync core config only (skip GitHub assets)
+- --outDir <dir>: write to another directory
+- --skip-overwrite: never overwrite existing files
+
+## workspace init (alias: ws init)
+
+Purpose: initialize workspace metadata such as README, package.json, pnpm change intent support, and issue template.
+Usage:
+
+- pnpm exec repo init
+- npx repoctl workspace init
+- npx repoctl ws init
+
+## workspace list (alias: ws ls)
+
+Purpose: list workspace packages for inspection or automation.
+Usage:
+
+- npx repoctl workspace list
+- npx repoctl ws ls --json
+- npx repoctl ws ls --json --out reports/workspaces.json
+  Options:
+- --json: emit structured workspace summary data
+- --out <file>: persist the current text or JSON output
+- --include-private: include private packages
+- --include-root: include the workspace root package
+- --pattern <glob>: add custom workspace globs; repeatable
+
+## tooling init (alias: tg init)
+
+Purpose: generate tooling config files plus matching devDependencies.
+Usage:
+
+- npx repoctl tooling init
+- npx repoctl tooling init eslint tsconfig vitest
+- npx repoctl tg init --all
+  Options:
+- --all: generate every built-in tooling config
+- --force: overwrite existing tooling config files
+  Notes:
+- Built-in tooling targets: commitlint, eslint, stylelint, lint-staged, tsconfig, vitest
+- Generated files also update root package.json devDependencies
+
+## workspace clean (alias: ws clean)
+
+Purpose: remove selected packages and update the repo helper package version.
+Usage:
+
+- npx repoctl workspace clean
+- npx repoctl ws clean
+  Options:
+- --yes: auto confirm
+- --include-private
+- --pinned-version <version>
+
+## env info (alias: e i)
+
+Purpose: print environment details for debugging and automation.
+Usage:
+
+- npx repoctl env info
+- npx repoctl e i --json
+- npx repoctl env info --json --out reports/env.json
+  Options:
+- --json: emit structured environment info
+- --out <file>: persist the current text or JSON output
+  Notes:
+- Includes cwd, workspace root, package manager, Node version, pnpm version,
+  platform, arch, and workspace package count.
+
+## env snapshot (alias: e s)
+
+Purpose: collect a combined debugging snapshot for issues, CI artifacts, or editor integrations.
+Usage:
+
+- npx repoctl env snapshot
+- npx repoctl e s --json
+- npx repoctl env snapshot --json --out reports/snapshot.json
+  Options:
+- --json: emit structured snapshot data
+- --out <file>: persist the current text or JSON output
+  Notes:
+- Includes `env info`, `doctor` report data, and the default `check` plan.
+
+## env mirror (alias: e m)
+
+Purpose: set VSCode binary mirror env.
+Usage:
+
+- npx repoctl env mirror
+- npx repoctl e m
+
+## skills sync
+
+Purpose: sync the `repoctl` skill into global agent skill directories.
+Usage:
+
+- pnpm exec repo skills sync
+- pnpm exec repo skills sync --codex
+- pnpm exec repo skills sync --claude
+- pnpm exec repo skills sync --cursor
+- pnpm exec repo skills sync --agents
+- pnpm exec repo skills sync --grok
+- pnpm exec repo skills sync --all
+
+## ai prompt create (aliases: ai p create, ai p new)
+
+Purpose: generate agentic prompt templates.
+Usage:
+
+- npx repoctl ai prompt create
+- npx repoctl ai p new --name checkout
+- npx repoctl ai prompt create --tasks agentic/tasks.json --format md -f
+  Options:
+- --output <path>
+- --force
+- --format <md|json>
+- --dir <path>
+- --name <name>
+- --tasks <file>
+  Notes:
+- If no --output or --name is set, it prompts for a folder and writes to
+  agentic/prompts/<timestamp>/prompt.md.
+- If --tasks is used, it expects a JSON array of strings or objects.
+
+## package create (alias: pkg new)
+
+Purpose: create a new package from a template.
+Usage:
+
+- npx repoctl new
+- npx repoctl package create [path]
+- npx repoctl pkg new [path]
+  Notes:
+- Prefer `repoctl new` for the lower-cost guided flow.
+- Prompts for a template choice unless defaults are set in repoctl.config.ts or monorepo.config.ts.
+- Explicit `--template` values are validated before writing files. Unknown keys
+  fail with the closest suggestion instead of silently falling back.
+- Use `--json` to print the resolved create plan for automation. It implies
+  `--dry-run` and does not write files.
+- Add `--out <file>` to write the preview or JSON plan to disk. It also implies
+  `--dry-run`.

package/assets/.agents/skills/repoctl/references/config.md

@@ -0,0 +1,67 @@
+# repoctl.config.ts
+
+Preferred filename: `repoctl.config.ts`
+
+Compatible legacy filename: `monorepo.config.ts`
+
+Rule:
+
+- `repoctl.config.*` has higher priority
+- `monorepo.config.*` remains supported
+- if both exist at the same time, CLI loading fails fast with an error
+
+Use `defineMonorepoConfig` to set default options for CLI commands.
+Only include the fields you need.
+
+Example:
+
+```ts
+import { defineMonorepoConfig } from 'repoctl'
+
+export default defineMonorepoConfig({
+  commands: {
+    ai: {
+      baseDir: 'agentic/prompts',
+      format: 'md',
+      force: false,
+      tasksFile: 'agentic/tasks.json',
+    },
+    create: {
+      defaultTemplate: 'tsdown',
+      renameJson: false,
+      templatesDir: 'packages/monorepo/templates',
+    },
+    clean: {
+      autoConfirm: false,
+      ignorePackages: ['docs'],
+      includePrivate: true,
+      pinnedVersion: 'latest',
+    },
+    upgrade: {
+      skipOverwrite: false,
+      targets: ['.github', 'repoctl.config.ts'],
+      mergeTargets: true,
+    },
+    init: {
+      skipReadme: false,
+      skipPkgJson: false,
+      skipChangeset: false,
+      skipIssueTemplateConfig: false,
+    },
+    mirror: {
+      env: {
+        VSCode_CLI_MIRROR: 'https://example.invalid',
+      },
+    },
+  },
+})
+```
+
+Key areas:
+
+- ai: default output, format, batch tasks
+- create: default template and template directory
+- clean: auto confirm and pinned version control
+- upgrade: overwrite behavior and extra targets
+- init: skip steps for README/package.json/pnpm change intent setup
+- mirror: add or override env mirrors

package/assets/.agents/skills/repoctl/references/templates.md

@@ -0,0 +1,46 @@
+# Templates
+
+Prefer `repo new [name]` for the guided flow. For agents, pass `--template`
+explicitly so the command does not prompt.
+
+Intent defaults:
+
+- library -> `tsdown` -> `packages/<name>`
+- web-app -> `vue-hono` -> `apps/<name>`
+- api-service -> `hono-server` -> `apps/<name>`
+- docs-site -> `vitepress` -> `apps/<name>`
+- cli-tool -> `cli` -> `apps/<name>`
+
+Run `repo templates` to discover template keys, categories, default targets, and
+descriptions. Use `repo templates <key>` for a single template detail page, and
+`repo templates --json` when scripting. Use `repo templates --check` to verify
+template metadata, directories, package.json files, duplicate targets, and
+temporary files; combine it with `--json` for CI. Use `repo templates --markdown`
+or `repo templates <key> --markdown` when generating documentation snippets.
+Add `--out <file>` to write the selected output to disk.
+
+Use `repo new <name> --template <key> --dry-run` to preview the target directory
+and package metadata without writing files. Use `repo new <name> --template <key>
+--json` when a script needs the same create plan as structured data; `--json`
+implies `--dry-run`. Add `--out <file>` to write either preview format to disk.
+
+Explicit template keys are validated before any files are written. If a key is
+misspelled, the CLI fails and prints the closest known key when one is available.
+
+Advanced users can still use `repo package create [path]` or `repo pkg new [path]`
+to select templates directly.
+
+Built-in template map:
+
+- tsdown -> templates/tsdown => packages/tsdown
+- vue-lib -> templates/vue-lib => packages/vue-lib
+- hono-server -> templates/server => apps/server
+- vue-hono -> templates/client => apps/client
+- vitepress -> templates/vitepress => apps/website
+- cli -> templates/cli => apps/cli
+
+Notes:
+
+- The command prompts for template selection unless defaults are set in
+  repoctl.config.ts or monorepo.config.ts.
+- Override mappings with `commands.create.templateMap` and `commands.create.templatesDir`.

package/assets/AGENTS.md

@@ -1,53 +1,42 @@
-# Repository Guidelines
+# Agent instructions
 
-## Project Structure & Module Organization
+This workspace is managed by **repoctl**. The recommended command is `repo`.
+Use `repoctl` only when a longer executable name is clearer. Do not treat this
+repository as the repoctl source project.
 
-This repository is the source workspace for repoctl, a task-first CLI for pnpm and Turborepo monorepos. Product packages live under `packages/`: `repoctl` is the recommended entrypoint, `monorepo` contains the core engine, `monorepo-templates` distributes managed assets, and the create packages provide primary and compatibility bootstrap commands. Private template source workspaces live under `templates/`; they are product assets, not independently published packages. Shared TypeScript and build settings live in root configs such as `turbo.json`, `tsconfig.json`, and `eslint.config.js`.
+## Create packages and apps
 
-## Build, Test, and Development Commands
+```bash
+pnpm exec repo templates
+pnpm exec repo new <name> --template <key>
+```
 
-- `pnpm install` — set up workspaces; ensure Node 22.12+ as defined in `package.json`.
-- `pnpm dev` — run `turbo run dev --parallel` for all apps that expose a `dev` script.
-- `pnpm build` — execute `turbo run build` to build every workspace with caching.
-- `pnpm test` / `pnpm test:dev` — run Vitest suites once or in watch mode across packages.
-- `pnpm lint` — invoke `turbo run lint` to apply ESLint/Stylelint policies repo-wide.
-- `pnpm repo:doctor` — diagnose the source workspace with the same repoctl entrypoint delivered to users.
-- `pnpm --filter @icebreakers/monorepo-templates sync:assets` — refresh the managed assets and template copies from repository sources.
+| Intent                   | Template key  |
+| ------------------------ | ------------- |
+| Vue / full-stack web app | `vue-hono`    |
+| API / Hono service       | `hono-server` |
+| TypeScript library / SDK | `tsdown`      |
+| Vue component library    | `vue-lib`     |
+| Documentation site       | `vitepress`   |
+| CLI                      | `cli`         |
 
-## Coding Style & Naming Conventions
+Preview without writing files: `pnpm exec repo new <name> --template <key> --dry-run`.
 
-Follow the root `.editorconfig`: two-space indentation, LF line endings, UTF-8. Prefer TypeScript (`.ts`/`.tsx`) and Vue SFCs; name files with kebab-case (`user-table.vue`) and exported symbols with PascalCase for components or camelCase for utilities. ESLint (`@icebreakers/eslint-config`) and Stylelint enforce formatting; run `pnpm lint` before committing, and rely on Husky + lint-staged to auto-fix staged files. Any style-related code changes (CSS, SCSS, Less, Vue style blocks, and similar files) must pass Stylelint checks before commit. All changed JavaScript, TypeScript, and Vue code must pass ESLint checks before commit.
+## Verify
 
-`lint-staged.config.js` must include Stylelint checks for staged style files so style validation also runs during pre-commit. It must also route staged TypeScript and Vue files into workspace `typecheck` scripts so Vue workspaces run `vue-tsc` and non-Vue TypeScript workspaces run `tsc`.
+```bash
+pnpm exec repo doctor
+pnpm exec repo check
+```
 
-When a single code file exceeds 300 lines, treat it as a refactor signal and split it into smaller modules before commit whenever the change touches that area. Do not keep appending responsibilities to an already large file when a folder-based split would make the design clearer.
+## Do not
 
-When splitting code, do not create suffix-based sibling files such as `xxx.config.ts` or `xxx.filter.ts` just to move logic around. Create a dedicated folder (for example `xxx/`) and place the split modules inside it with clear responsibilities.
+- Do not add packages by copying folders. Use `repo new`.
+- Do not hand-edit managed root configs that `repo init` / `repo upgrade` own.
+- Do not invent publish versions by hand. Use `pnpm change` for publishable packages.
 
-All generated code must pass ESLint checks, and all generated style files must pass Stylelint checks.
-Generated Vue files or other SFC files that include style blocks are also required to pass Stylelint checks.
+## Requirements
 
-## Testing Guidelines
-
-Vitest powers unit tests located in `test/*.test.ts`. Mirror existing naming by matching the unit under test (`monorepo` utilities map to `packages/monorepo/test/*.test.ts`). Aim for meaningful assertions rather than snapshot defaults, and add coverage checks with `pnpm test -- --coverage`, which writes reports to `coverage/`. When introducing new public APIs, include integration-style tests in the relevant app workspace. AI-assisted validation must run a full test matrix when available, including unit, integration, and E2E tests.
-
-Before running tests, build the packages first and run tests against build artifacts instead of source-only execution to better match real delivery behavior.
-
-TypeScript issues must be fixed before commit. Do not commit with unresolved TypeScript compile or type-check errors.
-
-TypeScript code must be validated with the relevant workspace `typecheck` script and must not contain type errors. Pure TypeScript workspaces are expected to validate with `tsc` (`pnpm typecheck` or `tsc -p tsconfig.json`). Vue workspaces are expected to validate with `vue-tsc` (typically `vue-tsc -b`).
-
-When building TypeScript libraries (type-focused APIs or public type definitions), add and maintain `tsd` type tests to verify exported type behavior.
-
-## Commit & Pull Request Guidelines
-
-Commits must conform to Conventional Commit syntax; recent history uses prefixes like `feat`, `fix`, and `chore`. Example: `feat(server): add auth router`. Use `pnpm commit` (commitlint prompt) or ensure your manual message passes `pnpm commitlint --edit`. Before opening a PR, make sure `pnpm lint` and `pnpm test` succeed, link related issues, and provide screenshots or logs for user-facing changes. Touching publishable packages requires a pnpm change intent (`pnpm change`) so releases stay traceable.
-
-For AI-generated or AI-assisted changes, use this verification order before commit or PR:
-
-1. Run build first (`pnpm build` or the relevant workspace build command).
-2. Run lint checks, ensuring all changed JavaScript, TypeScript, and Vue code passes ESLint and all style-related code passes Stylelint.
-3. Run TypeScript checks and fix all type errors before proceeding. Vue workspaces must pass `vue-tsc`; TypeScript workspaces must pass `tsc`.
-4. For TypeScript libraries, run `tsd` type tests and fix all failures before proceeding.
-5. Run tests against built artifacts, including unit, integration, and E2E suites (when available in the affected workspace).
-6. Before commit, review whether the touched files need splitting or refactoring; do not commit avoidable large-file growth when a clearer module boundary is apparent.
+- Node.js 22.13 or newer
+- pnpm
+- CLI output is English by default; `--lang zh-CN` or `REPOCTL_LANG=zh-CN` selects Simplified Chinese

package/assets/CLAUDE.md

@@ -0,0 +1,14 @@
+# Agent instructions
+
+This workspace is managed by **repoctl**. The recommended command is `repo`.
+
+Follow `AGENTS.md` in the workspace root. Create packages with
+`pnpm exec repo new <name> --template <key>`. Verify with
+`pnpm exec repo doctor` and `pnpm exec repo check`.
+
+If you were asked to create a new business project, do not add it inside an
+existing unrelated repository. Use:
+
+```bash
+pnpm create repoctl <dir> -- --yes --templates <keys>
+```

package/assets/gitignore

@@ -37,3 +37,6 @@ vite.config.ts.timestamp-*.mjs
 config.ts.timestamp-*.mjs
 .vite-inspect
 .playwright-cli
+
+# local AI task artifacts
+/.qoder/

package/assets/package.json

@@ -6,6 +6,7 @@
   "packageManager": "pnpm@12.3.4",
   "description": "Source workspace for repoctl and Icebreaker's shared development packages",
   "author": "ice breaker <hi@sonofmagic.top>",
+  "license": "MIT",
   "homepage": "https://repoctl.icebreaker.top",
   "repository": {
     "type": "git",
@@ -71,66 +72,25 @@
   },
   "devDependencies": {
     "@commitlint/cli": "^21.2.2",
-    "@eslint/config-inspector": "^3.4.0",
-    "@eslint/eslintrc": "^3.3.7",
+    "@eslint/config-inspector": "^3.4.1",
     "@icebreakers/commitlint-config": "workspace:*",
     "@icebreakers/eslint-config": "workspace:*",
-    "@icebreakers/stylelint-config": "workspace:*",
-    "@next/eslint-plugin-next": "^16.3.4",
-    "@prettier/plugin-xml": "^3.4.2",
-    "@tanstack/eslint-plugin-query": "^5.102.8",
-    "@types/eslint-plugin-tailwindcss": "^3.17.0",
-    "@types/fs-extra": "^11.0.4",
-    "@types/lodash": "^4.17.25",
-    "@types/lodash-es": "^4.17.12",
-    "@types/micromatch": "^4.0.10",
     "@icebreakers/monorepo": "workspace:*",
-    "@types/node": "^26.5.0",
-    "@types/semver": "^7.8.0",
-    "@types/set-value": "^4.0.3",
-    "@typescript-eslint/types": "^8.70.0",
-    "@unocss/eslint-plugin": "66.10.0",
+    "@icebreakers/stylelint-config": "workspace:*",
+    "@types/node": "^26.5.1",
     "@vitest/coverage-v8": "~5.0.0",
-    "astro-eslint-parser": "^3.1.0",
-    "ci-info": "^4.4.0",
-    "cross-env": "^10.1.0",
-    "defu": "^6.1.7",
-    "es-toolkit": "^1.52.0",
     "eslint": "^10.10.0",
-    "eslint-plugin-astro": "^3.1.0",
-    "eslint-plugin-mdx": "3.8.1",
-    "eslint-plugin-svelte": "^3.23.0",
     "execa": "^10.0.1",
-    "fast-glob": "^3.3.3",
-    "fs-extra": "^11.4.0",
-    "get-value": "^4.1.0",
     "husky": "^9.1.7",
-    "jiti": "^2.7.0",
-    "lint-staged": "^17.5.0",
-    "lodash": "^4.18.1",
-    "lodash-es": "^4.18.1",
-    "micromatch": "^4.0.8",
+    "lint-staged": "^17.5.1",
     "only-allow": "^1.2.2",
-    "pathe": "^2.0.3",
-    "pkg-types": "^2.3.3",
-    "prettier": "^3.9.6",
-    "prettier-plugin-astro": "^0.14.1",
     "repoctl": "workspace:*",
-    "rimraf": "^6.1.3",
-    "set-value": "^4.1.0",
     "stylelint": "^17.15.0",
-    "svelte": "^5.57.0",
-    "svelte-eslint-parser": "^1.8.1",
     "tailwindcss": "^4.3.3",
     "tsd": "^0.33.0",
     "tsdown": "0.23.0",
-    "tslib": "^2.8.1",
-    "tsx": "^4.23.13",
     "turbo": "^2.10.12",
-    "type-fest": "^5.9.0",
-    "tsup": "^8.5.1",
     "typescript": "^6.0.3",
-    "unbuild": "^3.6.1",
     "vitest": "~5.0.0",
     "yaml": "^2.9.0"
   },

package/assets/pnpm-workspace.yaml

@@ -17,7 +17,7 @@ allowBuilds:
 overrides:
   prettier: 3.9.6
   typescript: 6.0.3
-  vite: 8.2.2
+  vite: 8.3.0
   postcss: 8.5.28
   postcss-selector-parser: 7.1.6
   js-yaml: 5.4.1

package/assets/turbo.json

@@ -1,5 +1,8 @@
 {
   "$schema": "https://turborepo.com/schema.json",
+  "globalDependencies": [
+    "pnpm-lock.yaml"
+  ],
   "tasks": {
     "build": {
       "dependsOn": [
@@ -8,6 +11,10 @@
       "inputs": [
         "src/**",
         "lib/**",
+        "worker/**",
+        "wrangler.{json,jsonc,toml}",
+        ".dev.vars*",
+        ".env*",
         "package.json",
         "tsconfig*.json",
         "*.config.{js,ts,mjs,mts}"
@@ -72,6 +79,10 @@
       "inputs": [
         "src/**",
         "lib/**",
+        "worker/**",
+        "wrangler.{json,jsonc,toml}",
+        ".dev.vars*",
+        ".env*",
         "test/**",
         "package.json",
         "tsconfig*.json"

package/assets-data.mjs

@@ -13,6 +13,8 @@ const coreAssetTargets = [
   'repoctl.config.ts',
   'package.json',
   'AGENTS.md',
+  'CLAUDE.md',
+  '.agents',
   // pnpm
   'pnpm-workspace.yaml',
   // base tsconfig

package/dist/cli.mjs

@@ -1,4 +1,4 @@
-import { t as prepareAssets } from "./prepare-D7eJqEqy.mjs";
+import { t as prepareAssets } from "./prepare-zIcRa4-K.mjs";
 import process from "node:process";
 //#region src/cli.ts
 async function main() {

package/dist/index.mjs

@@ -1,4 +1,4 @@
-import { a as toPublishGitignorePath, c as assetsDir, d as templatesDir, f as assetTargets$1, i as isGitignoreFile, l as packageDir, n as createTemplateCopyFilter, o as toWorkspaceGitignorePath, p as getAssetTargets$1, r as shouldSkipTemplatePath, s as templateChoices$1, t as prepareAssets, u as skeletonDir } from "./prepare-D7eJqEqy.mjs";
+import { a as toPublishGitignorePath, c as assetsDir, d as templatesDir, f as assetTargets$1, i as isGitignoreFile, l as packageDir, n as createTemplateCopyFilter, o as toWorkspaceGitignorePath, p as getAssetTargets$1, r as shouldSkipTemplatePath, s as templateChoices$1, t as prepareAssets, u as skeletonDir } from "./prepare-zIcRa4-K.mjs";
 import path from "node:path";
 import fs, { access, open, rm } from "node:fs/promises";
 import exec from "nanoexec";