AI Web Design & Frontend Skills Catalog · Question revision 1 · Which ready-made AI agent skills are most useful for web design and frontend development, and when should you use each one?

13 October 2026 · Game UI source check

A mobile browser game is not a native mobile app.

Use Game UI Frontend only as a candidate for a browser-game HUD, menu, or overlay. The current skill source assumes a browser-game world in canvas or WebGL and text-heavy controls in the DOM. Its mobile instructions describe a narrower layout on a phone-sized browser viewport. They do not establish a workflow for a native iOS, Android, or React Native app.

Choose by the surface you actually have

1. Browser-game HUD: name the player action, camera mode, playfield area, persistent controls, and what a pause or inventory menu must do to input. The author’s prompt recipes show those fields. Trial the skill only if that workflow helps your task.
2. Ordinary web-app screen: give the agent the actual route, existing components, content, one visual reference, and the states you will inspect. Do not borrow a game HUD workflow to make a dashboard look less generic.
3. Native mobile app: look elsewhere. This catalogue has not established a ready-made skill fit for that platform.

Evidence limit: We read the current author files, not a pinned revision, and did not install Game Studio or run a game. The browser-game boundary is a source-scope inference, not a comparative result. An OpenAI Academy example describes using visual references and a project design.md with Codex; it is another workflow description, not proof that a no-skill brief wins.

The test still needed

Use the same playable browser-game fixture and acceptance checks with and without the skill. Check a known HUD obstruction, menu-to-camera input boundary, and desktop and mobile captures. Keep the loaded instructions and both runs’ versions, time, and visible results. We have not done that comparison, so the listing remains conditional.