Project Templates and create
Use project templates and create with the current published Askr packages.
@askrjs/askr0.0.59
How to use project templates and create
Start with this complete project templates and create shape, then replace the example data and application service with your own.
- Import the published @askrjs/askr entrypoint.
- Keep project templates and create configuration next to the component, route, or server composition root that owns it.
- Handle pending, unavailable, cancellation, and failure states, then verify the production path.
npx @askrjs/cli@0.0.5 create startkit my-app
npx @askrjs/cli@0.0.5 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. Passing no template name at all triggers interactive or prompt-based selection instead. 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 runs a dependency install for you after writing files, then prints npm run dev as the next step. Pass --no-install to skip that and get manual review instructions instead -- useful in CI, in sandboxed environments without network access, or when you want to inspect package.json before anything gets pulled down. If the install does run but fails, the CLI still reports success for the scaffold and prints the exact commands to finish setup by hand.
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.