Skip to main content
Agent skill

Verify Frontend

How to verify Massing web/viewer UI changes given that the dev-preview geometry loader stalls. Invoke when you changed apps/web and need to prove it works. Covers typecheck/lint/vitest/build, the tools-panel force-build technique, and honest flagging of flows you couldn't exercise.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Verify Frontend when an AI agent needs a reusable SKILL.md workflow for this job: How to verify Massing web/viewer UI changes given that the dev-preview geometry loader stalls. Invoke when you changed apps/web and need to prove it works. Covers typecheck/lint/vitest/build, the tools-panel force-build technique, and honest flagging of flows you couldn't exercise.

When not to use it

Skip Verify Frontend when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/verify-frontend
# Save SKILL.md to ~/.claude/skills/verify-frontend/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/verify-frontend/SKILL.md. For a shared project, commit the folder at .claude/skills/verify-frontend/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Verify Frontend skill for this task: Use Verify Frontend when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
59/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Verify a Massing frontend change

The dev-preview geometry loader **stalls at "preparing geometry"** for all model sizes, which blocks `loadProjectModel` and therefore `buildPanels` (the `panel-tree` model browser). But `buildToolsPanel` (the rail tools) can be forced. Verify what you can; flag what you can't.

## Always ``` cd apps/web && export PATH="/c/Program Files/nodejs:$PATH" npm run typecheck && npm run lint # eslint pinned to 9.39.5; Node 20 (Node 18 breaks build) npx vitest run <path/if/covered> npm run build # strongest compile check; ~1 min ```

## Force the tools rail to build (verifies rail UI live) The preview server is on :5173. In the running preview (via the browser tools), navigate to a project with a source IFC, then: ```js window.dispatchEvent(new CustomEvent('aec:persona', { detail: 'all' })); // forces buildToolsPanel + buildClashPanel // then read #panel-tools — the tool-group sections, buttons, inputs all render even though geometry stalled ``` This verifies: new rail tools/buttons/inputs, the ribbon tabs, the Library palette, the node-canvas launcher, the KEYS shortcut layer (dispatch KeyboardEvents), the Ask/analytical boxes. Exercise handlers by `.click()`ing buttons and reading the result-overlay / DOM.

## What you CAN'T verify live (flag it honestly) - `panel-tree` UI (the Project-Browser spine) — `buildPanels` never runs behind the stall. Verify its DOM-construction logic by reproducing it in the console instead, and say so. - End-to-end calls to NEW API routes against the dev API on **:8093** — that server is often a **stale process** predating your new routes → 404 there even though the client hits the right URL. Confirm via `read_network_requests` that the URL/payload is correct; the backend itself is covered by CI. (Restarting :8093 is the user's call.) - Anything geometry-coupled (placing an element, section cuts, camera).

## Report State exactly what was verified live vs. by typecheck/build vs. not exercised. Never claim an interactive viewer flow "verified" if the stall prevented it.

See memory: `tools-panel-verify-technique`, `web-build-needs-node-20`, `web-eslint-node-pin`, `dev-api-port`.

Intended uses

  • Use Verify Frontend when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.