# Project Templates and create

> Create a project from a template, or from a product prompt that picks the template and writes a build blueprint.

Source: [https://askrjs.com/docs/tooling/create](https://askrjs.com/docs/tooling/create)

Status: stable. Packages: @askrjs/askr.

**Published packages are authoritative.** Examples may lag behind a published contract. When guidance differs, verify the exports and TypeScript declarations in your installed package, then file an issue.

## Example

```sh
npx @askrjs/cli@latest create startkit my-app
npx @askrjs/cli@latest create --prompt "Authenticated operations dashboard"
```

## Published templates

askr create [template] <name> accepts one of five bundled templates: startkit, spa, ssr, ssg, and full-stack, stored under the package's templates/ directory. Interactive template selection only triggers when the name is also omitted (`askr create` with nothing) or when `--prompt` is passed — running `askr create my-app` with a name but no template silently defaults to startkit rather than asking, so name it explicitly if you don't want the default. Each template is a complete, runnable project -- there's no post-generation step where you delete demo code before it resembles a real app.

## Product prompts

askr create --prompt "<description>" [name] skips template selection entirely: the CLI reads the prompt text and deterministically picks the closest-fitting template, then writes .askr/blueprint.json and .askr/builder-brief.md capturing that decision so you (or an agent) can see the reasoning afterward. The same flag works alongside an explicit template name if you want to pin the template but still get a tailored blueprint. This is the path the docs recommend when you're not sure whether you need SSR, SSG, or a full-stack app yet.

## Install control

By default askr create stages a complete project, runs the dependency install, and publishes the project directory only after installation succeeds. Pass --no-install to skip installation and publish the scaffold for manual review instead -- useful in CI, offline environments, or when you want to inspect package.json first. If installation fails, the CLI removes the staged output, reports that no project files were published, and exits unsuccessfully.

## Agent skills

New projects get the bundled Askr skills copied into skills/ automatically as part of create, covering route-first structure, API integration, auth, realtime UX, accessibility, and more. Pass --no-skills to get a minimal scaffold without them -- for example if the target project already has its own skills/ conventions you don't want overwritten. You can always add them later with askr skills install.

## Documentation navigation

[Previous](https://askrjs.com/docs/tooling/cli-overview/index.md) | [Next](https://askrjs.com/docs/tooling/add/index.md)