\r \r

Role\r

\r This skill performs lightweight route and UI smoke validation. It is optimized for fast confidence on reachability, rendering, and navigation after changes that do not require a full deep-flow scenario.\r \r

When To Use\r

\r

• Use for route smoke checks, quick UI reachability checks, backend or frontend page rendering, and HTTP-level confidence validation.\r
• Use for keywords such as smoke, route check, page renders, HTTP request, 404, 405, and UI sanity.\r
• Use when the main question is “does the surface still load and route correctly?”\r \r

Source Material\r

\r

• AI-ENTRY.md\r
• CLAUDE.md\r
• dev/ai/skills/testing/SKILL.md\r
• dev/ai/skills/weline-routing/SKILL.md\r
• dev/ai/skills/module-development/SKILL.md\r \r

Responsibilities\r

\r

• Prove route registration and basic page reachability quickly.\r
• Check for obvious backend, frontend, or API regressions.\r
• Choose HTTP or browser-smoke validation proportional to the change.\r
• Catch route wiring issues before deeper acceptance work begins.\r \r

Workflow\r

\r

1. Identify the changed route, page, or UI surface.\r
2. Determine whether HTTP-level validation is enough or whether a browser smoke is needed.\r
3. Refresh route registration if the change requires it.\r
4. Run http:request or a minimal E2E smoke path against the affected surface.\r
5. Check response reachability, basic rendering, and obvious route failures.\r
6. Re-run the narrow smoke after fixes.\r
7. Return the route path, command, and observed result.\r \r

Weline Rules\r

\r

• Do not use routes.xml.\r
• Run php bin/w setup:upgrade --route when route registration changed.\r
• Provide HTTP or E2E validation evidence where relevant.\r
• Do not use default WLS port 9501 for AI testing when isolated runtime validation is required.\r \r

Inputs Required\r

\r

• The affected route, controller, page, or API path.\r
• Whether the change is frontend, backend, or API.\r
• Any login or runtime prerequisite for the smoke path.\r
• Expected basic success condition.\r \r

Expected Output\r

\r

• A fast smoke-validation result for the changed route or UI surface.\r
• The exact command or minimal browser path used.\r
• A concise statement of pass, failure, or follow-up required.\r \r

Validation\r

\r

• Run php bin/w http:request ... for direct route checks when appropriate.\r
• Run the smallest browser smoke path when rendering or navigation must be seen.\r
• Confirm route refresh was performed if registration changed.\r
• Confirm obvious 404, 405, auth, or render failures are surfaced clearly.\r \r

Constraints\r

\r

• Do not confuse smoke validation with full end-to-end coverage.\r
• Do not skip route refresh when the route graph changed.\r
• Do not treat a reachable page as proof that deeper business logic is correct.\r
• Do not use heavyweight browser suites when one focused smoke check is enough.\r \r