Pixijs Create
Scaffold a new PixiJS v8 project or add PixiJS to an existing repo using create-pixi and the documented template presets.
Overview
PixiJS Create is an agent skill for the Build phase that scaffolds PixiJS v8 projects with create-pixi templates or adds pixi.js to existing apps.
Install
npx skills add https://github.com/pixijs/pixijs-skills --skill pixijs-createWhat is this skill?
- Official `npm create pixi.js@latest` flow with npm, yarn, pnpm, or bun
- Non-interactive scaffold via `--template` (bundler-vite, bundler-webpack, bundler-esbuild, bundler-import-map, creation-
- Node 18+ or 20+ requirement and `npm install pixi.js` path for existing projects
- Post-scaffold install plus dev script workflow documented end-to-end
- Documents Vite top-level-await production-build gotcha for creation templates
- 7 named template presets: bundler-vite, bundler-webpack, bundler-esbuild, bundler-import-map, creation-web, framework-re
- Requires Node.js 18+ or 20+
Adoption & trust: 1.3k installs on skills.sh; 206 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want a PixiJS v8 repo but do not know which official template, package manager command, or Node version matches your bundler or React setup.
Who is it for?
First-time Pixi v8 setup with official templates and non-interactive CI-friendly `--template` flags.
Skip if: Runtime rendering APIs, blend modes, asset loading pipelines, or production performance optimization after the repo exists.
When should I use this skill?
User asks to create pixi.js, npm create, scaffold, template, bundler-vite, new project, quick start, or npm install pixi.js on existing project.
What do I get? / Deliverables
You get a generated project folder or install instructions plus dev-script steps so you can open the canvas and implement gameplay next.
- Scaffolded Pixi project directory
- Documented dev run commands
Recommended Skills
Journey fit
Build is the canonical phase because the skill only helps you start or wire a rendering codebase—not ship, launch, or operate it. Frontend subphase covers bundler templates (Vite, Webpack, esbuild), creation-web, and framework-react game or canvas apps.
How it compares
Official scaffold CLI reference—not a game design or asset authoring skill.
Common Questions / FAQ
Who is pixijs-create for?
Indie game and web graphics builders who need a correct PixiJS v8 folder structure and dev server before writing scenes and loaders.
When should I use pixijs-create?
At Build/frontend when starting create pixi.js, choosing bundler-vite vs framework-react, or adding npm install pixi.js to an existing project.
Is pixijs-create safe to install?
It documents standard npm create flows; review the Security Audits panel on this page and verify template output before committing secrets or deploying.
SKILL.md
READMESKILL.md - Pixijs Create
`create pixi.js` is the official CLI for scaffolding a new PixiJS v8 project. Run it with any package manager (`npm`, `yarn`, `pnpm`, `bun`) and pick a template from the interactive menu, or pass `--template` to skip prompts. It writes a self-contained project folder; you then `cd` in, install dependencies, and run the dev script. ## Quick Start Scaffold a new project with interactive prompts: ```bash npm create pixi.js@latest ``` Or skip prompts by passing a project name and template: ```bash npm create pixi.js@latest my-game -- --template bundler-vite ``` Then: ```bash cd my-game npm install npm run dev ``` Requires Node.js 18+ or 20+. Some templates (notably `creation-web` and `framework-react`) may require a newer Node version; the package manager will warn if so. ### Adding PixiJS to an existing project If you already have a bundler, framework, or project set up, skip the CLI and install the package directly: ```bash npm install pixi.js ``` Then import from `pixi.js` and construct an `Application` as shown in `pixijs-application`. The CLI templates are a convenience for new projects; they don't add anything to the library that `npm install pixi.js` can't give you. **Related skills:** `pixijs-application` (how the scaffolded `new Application()` + `app.init()` entry point works), `pixijs-core-concepts` (renderers and the render loop), `pixijs-scene-core-concepts` (scene graph fundamentals for the first things you'll add to the stage), `pixijs-assets` (loading textures, fonts, and bundles the template expects you to drop into `public/` or `src/assets/`). ## Core Patterns ### Choose a package manager The command is the same shape for every package manager: ```bash npm create pixi.js@latest yarn create pixi.js pnpm create pixi.js bun create pixi.js ``` Under npm 7+ you must pass a `--` before CLI flags so npm doesn't consume them: ```bash npm create pixi.js@latest my-game -- --template bundler-vite ``` Yarn, pnpm, and bun don't need the extra separator: ```bash yarn create pixi.js my-game --template bundler-vite pnpm create pixi.js my-game --template bundler-vite bun create pixi.js my-game --template bundler-vite ``` Use `.` as the project name to scaffold into the current directory. ### Interactive flow Running with no arguments walks through prompts: 1. Project name (defaults to `pixi-project`). 2. Framework / template category. 3. Variant (TypeScript vs JavaScript where applicable). 4. Whether to install dependencies immediately (some runners). At the end, the CLI prints the `cd` + install + dev commands for the manager you invoked it with. ### Non-interactive flow Pass a project name and `--template` to skip all prompts. This is the form you want for scripts, CI, and quickstart docs: ```bash npm create pixi.js@latest my-game -- --template bundler-vite ``` ### Available template presets Templates fall into two categories: - **Bundler templates** (`bundler-*`): generic PixiJS setup wired up with your bundler of choice. Use one of these when you want to pick your own structure. - **Creation templates** (`creation-*`): platform-tailored starters with extras already wired in (AssetPack, sound, UI, scene routin