Add Test Page

Use this skill when the user asks to add a standalone validation page, demo route, smoke test page, or an isolated visual verification surface.

Branch Rule

• Do not add architecture validation pages directly on the main product branch.
• Prefer a dedicated spike branch such as spike/tailwind-v4-lab or spike/router-layout-check.
• If the current branch is intended for production-facing work, move the validation work to a spike branch before adding temporary pages or routes.

Repo Contract

• The home route is not a test page. Keep / reserved for the product-facing homepage or dashboard.
• Temporary validation routes must not become the default entry path of the app.
• Keep experiment code visibly isolated under a temporary area such as src/spikes/<topic>/.
• Name temporary routes clearly, for example /__spike/tailwind-v4 or /__spike/router-layout.
• Keep the page self-contained. Use inline mock data or local state instead of real APIs unless the feature explicitly requires integration verification.