
Use Template
- 428 installs
- 305 repo stars
- Updated May 25, 2026
- opusgamelabs/game-creator
use-template is an agent skill that clones a game-creator gallery template into a new browser game project for developers who need working Phaser or Three.js boilerplate in seconds instead of manual scene scaffolding.
About
use-template is skill version 1.3.0 in OpusGameLabs/game-creator for fast game bootstrapping from a curated template gallery. Invoke it with /use-template [template-id] [project-name] when the user says use a template, clone flappy-bird, or start from the platformer example. The skill copies template source from site/manifest.json—a 20-entry catalog with id, name, engine, genre, complexity, features, and demo URLs—updates package.json and title, then runs npm install so npm run dev starts immediately. Game-creator documents this as a roughly 10-second copy versus the longer viral-game or make-game pipelines. MIT licensed with tags game, template, scaffold, clone, and gallery. Reach for use-template when prototyping a browser game from an existing Phaser 3 or Three.js example rather than authoring scenes, assets, and boilerplate from scratch.
- Maps game ideas to the right built-in template
- Explains required files, folders, and entry points
- Shows how to swap assets and tweak starter scenes
- Documents common customization pitfalls
- Speeds first playable without breaking template conventions
Use Template by the numbers
- 428 all-time installs (skills.sh)
- +11 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #51 of 247 Game Development skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/opusgamelabs/game-creator --skill use-templateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 428 |
|---|---|
| repo stars | ★ 305 |
| Last updated | May 25, 2026 |
| Repository | opusgamelabs/game-creator ↗ |
How do you bootstrap a browser game from a template?
Bootstrap a new browser game from game-creator templates instead of scaffolding scenes, assets, and boilerplate from scratch.
Who is it for?
Developers starting browser games who want a working Phaser 3 or Three.js template clone before customizing gameplay or art.
Skip if: One-shot AI-generated games from a single prompt—use viral-game or make-game—or non-browser native game engines outside game-creator templates.
When should I use this skill?
The user says use a template, clone a gallery game, start from flappy-bird or platformer, or wants to bootstrap a game without scaffolding from scratch.
What you get
Copied game project directory with updated package.json, installed dependencies, and runnable dev server from a gallery template source.
- cloned game project
- updated package.json
- installed node_modules
By the numbers
- Skill version 1.3.0 clones projects from a 20-entry game template gallery manifest
- Documented as a ~10-second template copy versus longer make-game pipelines
Files
Use Template
Clone a game template from the gallery into a new project. This is a fast copy — working code in seconds, not an AI pipeline.
Behavior
1. Parse arguments: <template-id> [project-name]
- If no arguments provided, read
site/manifest.json, display a numbered list of all templates with their engine/complexity/description, and ask the user to pick one. template-idis required.project-namedefaults totemplate-id.
2. Look up template in site/manifest.json by id. If not found, show available IDs and abort.
3. Determine target directory:
- If current working directory is inside the
game-creatorrepository →examples/<project-name>/ - Otherwise →
./<project-name>/ - If target already exists, abort with error.
4. Copy the template source directory to the target, excluding:
node_modules/dist/output/.herenow/progress.mdtest-results/playwright-report/
5. Update project metadata:
- In
package.json: set"name"to the project name - In
index.html(if exists): update<title>to a formatted version of the project name
6. Install dependencies: Run npm install in the target directory.
7. Print next steps:
Template cloned successfully!
cd <project-name>
npm run devImplementation
const fs = require('fs');
const path = require('path');
const { execSync } = require('child_process');
// Find game-creator root (contains site/manifest.json)
function findRoot(dir) {
let d = dir;
while (d !== path.dirname(d)) {
if (fs.existsSync(path.join(d, 'gallery', 'manifest.json'))) return d;
d = path.dirname(d);
}
return null;
}
const root = findRoot(process.cwd());
const manifest = JSON.parse(fs.readFileSync(path.join(root, 'gallery', 'manifest.json'), 'utf-8'));
// Parse args
const [templateId, projectName] = args; // provided by the agent
const template = manifest.find(t => t.id === templateId);
const name = projectName || templateId;
// Validate project name — reject path traversal and special characters
if (/[\/\\]|^\.\.?$|\.\./.test(name)) {
throw new Error(`Invalid project name: "${name}". Must not contain path separators or ".." sequences.`);
}
if (!/^[a-zA-Z0-9][a-zA-Z0-9._-]*$/.test(name)) {
throw new Error(`Invalid project name: "${name}". Use only alphanumeric characters, hyphens, underscores, and dots.`);
}
// Determine target
const inGameCreator = process.cwd().startsWith(root);
const target = inGameCreator
? path.join(root, 'examples', name)
: path.join(process.cwd(), name);
// Verify resolved path stays within expected parent directory
const expectedParent = inGameCreator ? path.join(root, 'examples') : process.cwd();
if (!path.resolve(target).startsWith(path.resolve(expectedParent))) {
throw new Error('Target directory resolved outside expected parent. Aborting.');
}
// Copy with exclusions
const EXCLUDE = ['node_modules', 'dist', 'output', '.herenow', 'progress.md', 'test-results', 'playwright-report'];
function copyDir(src, dst) {
fs.mkdirSync(dst, { recursive: true });
for (const entry of fs.readdirSync(src, { withFileTypes: true })) {
if (EXCLUDE.includes(entry.name)) continue;
const s = path.join(src, entry.name);
const d = path.join(dst, entry.name);
if (entry.isDirectory()) copyDir(s, d);
else fs.copyFileSync(s, d);
}
}
copyDir(path.join(root, template.source), target);
// Update package.json
const pkgPath = path.join(target, 'package.json');
if (fs.existsSync(pkgPath)) {
const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf-8'));
pkg.name = name;
fs.writeFileSync(pkgPath, JSON.stringify(pkg, null, 2) + '\n');
}
// Update index.html title
const indexPath = path.join(target, 'index.html');
if (fs.existsSync(indexPath)) {
let html = fs.readFileSync(indexPath, 'utf-8');
const prettyName = name.replace(/[-_]/g, ' ').replace(/\b\w/g, c => c.toUpperCase());
html = html.replace(/<title>[^<]*<\/title>/, `<title>${prettyName}</title>`);
fs.writeFileSync(indexPath, html);
}
// Install
execSync('npm install', { cwd: target, stdio: 'inherit' });
// Optional anonymous telemetry — tracks which templates are popular
// Data sent: event type ("clone"), template ID, source ("skill"), schema version
// No PII, IP addresses, file paths, or user-identifiable data is transmitted
// Opt out: set DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 in your environment
if (!process.env.DO_NOT_TRACK && !process.env.DISABLE_TELEMETRY) {
const https = require('https');
const telemetryUrl = process.env.TELEMETRY_URL || 'https://gallery-telemetry.up.railway.app';
https.get(`${telemetryUrl}/t?event=clone&template=${encodeURIComponent(templateId)}&source=skill&v=1`)
.on('error', () => {});
}Example Usage
/use-template flappy-bird my-game
/use-template threejs-3d-starter space-shooter
/use-template castle-siegeSecurity Notes
- Path validation: Project names are validated to reject path traversal (
..), path separators, and special characters. The resolved target path is verified to stay within the expected parent directory. - npm install: Runs
npm installfrom the copied template'spackage.json, which contains only pinned dependencies from the template (Phaser/Three.js, Vite). No arbitrary packages are installed. - Telemetry: Anonymous, opt-out usage telemetry sends only the template ID and event type (no PII, paths, or user data). Disable with
DO_NOT_TRACK=1orDISABLE_TELEMETRY=1environment variables. - Template source: Templates are copied from the local
site/manifest.jsonregistry within the plugin — no external templates are fetched at clone time.
Key Difference from /viral-game and /make-game
/use-template is a 10-second copy. You get working, runnable code instantly and customize it manually. /viral-game is a 10-minute AI pipeline that scaffolds, designs, adds audio, tests, deploys, and monetizes from a text prompt or tweet URL — opinionated and one-shot. /make-game is the deeper, multi-session game-dev workflow with milestones, ADRs, and docs/STATE.md for projects that need to evolve over time.
Related skills
How it compares
Pick use-template for instant gallery clones; use make-game or viral-game when generating a custom browser game through the full agent pipeline.
FAQ
How is use-template different from make-game?
use-template performs a fast gallery copy—working code in seconds—while make-game and viral-game run longer milestone-driven or one-shot generation pipelines. Pick use-template when an existing template fits the starting point.
How many templates does use-template support?
use-template reads from site/manifest.json in game-creator, which lists 20 gallery entries with id, engine, genre, complexity, and source paths for clone operations.