菜单
Use when creating, changing, auditing, or reviewing PAW Forkd webapp controllers, forms, validators, JSP/JSTL views, i18n bundles, Spring Security routes, webapp CSS/JS, uploads, redirects, MVC tests, REST resources, API error mapping, CORS, WAR asset integration, or SPA static-hosting work across TP1 and TP final.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
| name | paw-webapp-layer |
| description | Use when creating, changing, auditing, or reviewing PAW Forkd webapp controllers, forms, validators, JSP/JSTL views, i18n bundles, Spring Security routes, webapp CSS/JS, uploads, redirects, MVC tests, REST resources, API error mapping, CORS, WAR asset integration, or SPA static-hosting work across TP1 and TP final. |
Use this for webapp/: TP1 controllers, forms, validation, JSP/JSTL, i18n, Spring Security, filters, webapp CSS/JS, and MVC tests. In TP final, use it for REST resources, API error mapping, auth/web security, CORS, SPA static hosting, and WAR asset integration after $paw-tp-final-migration sets the plan. Use $paw-frontend-layer for SPA source under frontend/.
Read references/layer-rules.md before editing webapp.
CLAUDE.md, affected controller/form/JSP/tests, and DESIGN.md for UI changes; for TP final also read resumen-final-paw-2026 and checklist-tp-final-rest-spa.WebAuthConfig plus AccessHelper expressions; update JSP visibility with Spring Security taglib when JSP remains.<c:out>, <c:url>, <spring:message>, and private views under WEB-INF.$paw-tp-final-migration: REST contract, SPA route/static hosting, tests, and rollback state must match that slice.$paw-frontend-layer.java.sql, business orchestration, or domain ownership decisions in controllers.${...} for dynamic user content; use <c:out> or escaping helpers.SafeRedirectPathValidator.@PreAuthorize with URL rules unless the existing flow already chose that pattern.forkd.css before adding local markup or inline styles.DESIGN.md first.$paw-tp-final-migration first; do not graft a frontend build or JWT flow into TP1 by accident.frontend/, use $paw-frontend-layer; webapp owns hosting/integration, not component/store/router implementation./api/*, expose DTOs/forms only, and build Location, relation links, Link, and ETag with request-aware URI helpers.type, title, status, detail, instance); /api/* 404 stays JSON, while SPA fallback serves index.html only for non-API deep links.Location, Link, ETag, X-Access-Token, or X-Refresh-Token, expose them explicitly through CORS.ETag/If-None-Match/304) only when semantically valid. Cache only hashed static assets as long-lived immutable; keep index.html/root revalidated or short-lived.index.html, hashed JS/CSS/assets, and backend classes; Maven must build frontend before webapp.WEB-INF/views/shared/restaurant-form-body.jspf; keep them aligned.MultipartRequestSizeFilter and ErrorHandlingAdvice.mvn -pl webapp -am -Dtest=<MvcTestName> -Dsurefire.failIfNoSpecifiedTests=false test.mvn -pl webapp -am test.mvn clean test.mvn clean package, then inspect the WAR for index.html, JS/CSS/assets, and WEB-INF/classes.jar tf webapp/target/*.war | rg '(^|/)index.html$|assets/|static/|WEB-INF/classes'.mvn -pl webapp -am jetty:run -Dsecurity.rememberme.key="$(openssl rand -base64 48)".Use when planning, implementing, auditing, reviewing, or closing a PAW TP final migration to REST API plus SPA/frontend, especially when the user says TP final, final delivery, pass the app to final, replace MVC/JSP with API+SPA, add Jersey/JAX-RS resources, stateless auth, frontend build, routing/state/forms/i18n/testing, Maven/WAR integration, PostgreSQL data preservation, prior-feedback closure, performance/cache, deployment, or delivery readiness.
Use when planning, implementing, auditing, or reviewing PAW Forkd features in a PAW app checkout across TP1, TP2, or TP final; routes by project stage, Maven modules, PAW-Wiki rules, Superpowers workflows, layer-specific skills, and migration skills.
Use when creating, changing, auditing, or reviewing PAW TP final SPA frontend source, routes, API clients, stores/composables, forms, auth state, i18n catalogs, frontend tests, build config, static assets, or context-path/base-path behavior.
Use when creating, changing, auditing, or reviewing PAW Forkd service interfaces, command DTOs, public service contracts, business exceptions, mail service contracts, or API-facing service boundaries across TP1, TP2, and TP final.
Use when creating, changing, auditing, or reviewing PAW Forkd service implementations, business rules, transactions, scheduler jobs, mail rendering/sending, services-layer tests, or service behavior affected by TP2 JPA/TP final API migrations.
Use when creating, changing, auditing, or repairing PAW Forkd blackbox tests, Maven verification gates, test fixtures, HSQLDB/JPA persistence tests, service tests, MVC/security/API tests, template/frontend tests, or test failures.