Skip to content

xtarter · two tools, one standard

Start conformant.Stay conformant.

Scaffold new JavaScript and TypeScript projects with create-xtarter-app. Bring existing repos up to standard with xtarterize. Both paths give you Biome, strict TypeScript, CI, and editor configs that hold their shape.

why conformant

Standards that hold their shape

Configs drift when enforcement lives in someone's head. Someone formats locally, CI disagrees, reviews turn into style debates. This baseline lives in the repo instead.

  • Reviews that read themselves

    Biome and strict TypeScript run from the first commit. Pull requests argue about features, not formatting.

  • CI that stays green

    GitHub Actions runs the same configs your editor enforces. Local and CI cannot disagree about what passing means.

  • Agent-ready by default

    Agent skills ship next to every config, so AI assistants working in your repo follow the same standard you do.

All source repositories on GitHub

The project lifecycle

Two tools, one path from first commit to shipped project.

  1. Choose
  2. Scaffold
  3. Conform
  4. Ship

Pick your door.

Both commands land on the same baseline. Scaffold something new, or conform code you already have.