web-game-foundations Skill
Set browser-game architecture before implementation. Use when the user needs engine choice, simulation and render boundaries, input model, asset organization, or save/debug/performance strategy. Published by openai in plugins.
Decision snapshot
Is this a fit?
Browser automation, Design and media, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is web-game-foundations Skill?
Set browser-game architecture before implementation. Use when the user needs engine choice, simulation and render boundaries, input model, asset organization, or save/debug/performance strategy. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Browser automation
- Design and media
- Browser automation use cases
- Design and media use cases
Declared skill metadata
- Source file: plugins/game-studio/skills/web-game-foundations/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use web-game-foundations Skill
- Use it for browser automation.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/game-studio/skills/web-game-foundations/SKILL.md
What it does
Set browser-game architecture before implementation. Use when the user needs engine choice, simulation and render boundaries, input model, asset organization, or save/debug/performance strategy.
Skill instructions
Web Game Foundations Overview Use this skill to establish the non-negotiable architecture before implementation starts. Browser games degrade quickly when simulation, rendering, UI, asset loading, and input handling are mixed together. Default rule: simulation state is owned outside the renderer, browser UI is not forced into the canvas unless there is a clear reason, and shipped 3D assets default to GLB or glTF 2.0 rather than ad hoc model formats. Use This Skill When - the user has not settled the engine or renderer choice - the task is about boundaries, module shape, state ownership, or asset policy - multiple specialist skills need one shared architectural frame Do Not Stay Here When - the runtime track is clearly Phaser - the runtime track is clearly vanilla Three.js - the runtime track is clearly React Three Fiber - the task is purely about shipped 3D assets Once the stack is clear, hand off to the runtime or asset specialist skill. Architecture Rules 1. Separate simulation from
Verified compatibility and discovery
Frequently asked questions
What is web-game-foundations?
web-game-foundations is a open-source AI agent skill with Copy skill directory. Set browser-game architecture before implementation. Use when the user needs engine choice, simulation and render boundaries, input model, asset organization, or save/debug/performance strategy.
Who is web-game-foundations best for?
web-game-foundations is best for reusing agent instructions, scripts, and references, browser automation workflows, design and media workflows.
How do I install web-game-foundations?
Install or run web-game-foundations using Copy skill directory. Check web-game-foundations for the latest setup command.
Is web-game-foundations actively maintained?
web-game-foundations may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
