| name | autojudge-web-changes |
| description | Use when modifying AutoJudge web pages, Mustache views, template descriptors, browser component classes, frontend models, or Webpack-built assets in web/. |
| user-invocable | true |
| argument-hint | Web page, component, template, or bundle change to implement or review |
AutoJudge Web Changes
Use this skill for frontend and SSR work in web/.
What To Inspect First
- The page route in
web/app.js.
- The matching entrypoint in
web/src/js/.
- Any shared browser class in
web/src/js/components/, model/, or helpers/.
- The related
web/template/*.js and web/view/*.html files.
Workflow
- Change source files in
web/src/ rather than generated bundles in web/public/.
- Keep hydration data flowing through
res.templateRender(...) and template descriptors.
- Reuse frontend model and helper layers for API access instead of scattering new network code.
- Rebuild the touched bundle with
cd web && npx webpack --mode production when source changes are meant to ship.
- Report whether browser validation was performed, since many web behaviors here are runtime and environment dependent.
Notes
- The app is server-rendered with Express and Mustache, then enhanced with vanilla JS entrypoints.
LOCAL_SERVER changes auth and API URL behavior, so login flows can differ between local contest mode and hosted mode.
- Use
AGENTS.md for shared commands and environment constraints.