Frontend task routing
Read this plugin only when its listed skills match the current task. Discover the actual client tools, account access and permission requirements before invoking anything. Treat this directory as bundled source, not proof of an installed or authenticated integration.
Select one entrypoint
| Skill | Apply it to |
|---|---|
| develop-web-game | Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with render_game_to_text. |
| web-html | Build semantic, accessible HTML documents and static templates with standards-compliant structure, predictable form behavior, and ARIA-aware markup |
| web-htmx | Build server-driven HTMX interfaces with progressive enhancement, explicit fragment contracts, and minimal custom JavaScript |
| web-nextjs | Build and troubleshoot Next.js applications with app router boundaries, SSR/ISR behavior, and server/client separation |
| web-nuxt | Build and maintain Nuxt applications with explicit runtime configuration, rendering-mode decisions, and deployment-safe defaults |
| web-react | Use this skill for build, refactor, and review React component systems, hooks, and client-side UI architecture with performance-aware rendering and predictable state boundaries |
| web-sveltekit | Build and maintain SvelteKit applications with clear route/load boundaries, adapter setup, and runtime configuration |
| web-vue | Build Vue applications with Composition API patterns, state-flow discipline, and reusable component boundaries |
Preserve the integration boundary
Read only the references required by the selected skill. Inspect bundled scripts before execution; retain their argument and output contracts. Keep credentials and private payloads out of examples, logs and ambient hook context.
Do not install, enable, trust, publish or update a remote integration merely because you edit these files. Keep canonical and authorized bundled mirrors coherent, preserve existing resource paths and license notices, and report the checks you actually performed. Local packaging does not assert vendor endorsement.