Configuration

No config file is required. xtarterize detects your stack and applies only what fits.

Detection

xtarterize reads package.json, lockfiles, config files, and directories to determine your framework, bundler, router, styling, package manager, monorepo status, and existing configs.

• Framework, bundler, router, styling, and TypeScript come from dependencies and devDependencies.
• The package manager comes from the lockfile: pnpm-lock.yaml, yarn.lock, package-lock.json, bun.lock, or bun.lockb.
• Monorepo status, GitHub, and existing configs come from the file system.

Note

If react and react-native or expo are both present, the project is treated as React Native.

Task gating

• Vite plugin tasks need a browser Vite project
• Monorepo tasks need a detected monorepo
• CI tasks need a GitHub repository
• TypeScript tasks need TypeScript

In monorepos, tasks are also filtered by scope. See the monorepo guide.

Task selection

.xtarterizerc accepts skip and only arrays, and the same fields work under the "xtarterize" key in package.json.

{
  "skip": ["agent/skills-install"],
  "only": ["ts/strict", "lint/biome"]
}

• CLI --only replaces the config only list
• CLI --skip adds to the config skip list
• skip wins when a task is in both lists
• An absent or empty only list imposes no restriction

For command behavior, see the CLI reference; for generated files, see the task catalog.