메뉴
Standardized Phaser scene template with test seam, lifecycle methods, and common patterns. Use when creating new Phaser scenes to ensure consistency, test seam setup, and proper lifecycle management. Provides template code for new scenes.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/pmarashian/cursor-agent-skills --skill phaser-scene-template명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Setup and patterns for a Vite + React frontend with Capacitor and Ionic React, plus a separate Next.js backend in a monorepo. Use when creating or modifying a Capacitor mobile app with a Vite frontend and Next.js API, or when adding Capacitor to an existing Vite app with a Next.js backend.
Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | phaser-scene-template |
| description | Standardized Phaser scene template with test seam, lifecycle methods, and common patterns. Use when creating new Phaser scenes to ensure consistency, test seam setup, and proper lifecycle management. Provides template code for new scenes. |
Standardized Phaser scene template with test seam, lifecycle methods, and common patterns. Accelerate scene creation and ensure consistency.
See assets/scene-template.ts for complete scene template code.
preload(), create(), update()Every scene MUST include test seam setup:
window.__TEST__ availabilitywindow.__TEST__.commands objectgameState() method for state accesswindow.__TEST__.ready = true after initializationwindow.__TEST__.sceneKeyExample:
setupTestSeam() {
if (!window.__TEST__) {
window.__TEST__ = {};
}
window.__TEST__.sceneKey = this.scene.key;
window.__TEST__.ready = true;
window.__TEST__.commands = {
goToScene: (key: string) => {
this.scene.start(key);
},
gameState: () => {
return {
scene: this.scene.key,
score: this.score,
// Scene-specific state
};
}
};
}
If test seam not working:
window.__TEST__ is definedcreate() method)window.__TEST__.ready === truewindow.__TEST__.commandsCommon test seam issues:
create() methodwindow.__TEST__.commandsVerify test seam setup:
// In browser console or test
console.log(window.__TEST__); // Should be defined
console.log(window.__TEST__.ready); // Should be true
console.log(window.__TEST__.sceneKey); // Should match scene key
console.log(window.__TEST__.commands); // Should have commands
Test seam command verification:
# In agent-browser
agent-browser eval "window.__TEST__ && window.__TEST__.ready"
agent-browser eval "window.__TEST__.commands.gameState()"
agent-browser eval "window.__TEST__.commands.goToScene('MainMenu')"
See references/lifecycle-patterns.md for detailed lifecycle patterns:
preload() - Load assetscreate() - Initialize scene, set up test seamupdate() - Game loopassets/scene-template.ts to your scene fileWhen the scene's purpose is to test a single UI component, use the same lifecycle and test seam checklist but with minimal content: only that component plus the test seam. For the full workflow and naming (e.g. ComponentNameTestScene, boot via ?scene=...), use the phaser-component-test-scenes skill.
assets/scene-template.ts - Template code for new scenesreferences/lifecycle-patterns.md - preload, create, update patterns