agentleFS
RorroRojas3RorroRojas3/maf-agents/.claude/skills/inspector-workbench/SKILL.md

inspector-workbench

Skill0 starsChanged 2 months agoMITView on GitHub

Runs Inspector UI work on the standalone Threads state lab so the agent can see the overlay. Use when a CopilotKit employee asks an agent to fix, polish, add, or debug Inspector UI, chrome, panes, overlay actions, launcher, Home, Threads, Playground, Memory, or any visual behavior in @copilotkit/web-inspector. Don't use for docs-only Callout updates (load inspector-docs), runtime or core changes with no Inspector UI, showcase cell work, or reading Inspector as a consumer inside an app.

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. About 0 are common, 14 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not load it for docs-only Callout work.

    line 28
  2. Distinctive:

    Do not start a showcase app, an example app, or Storybook as the default host.

    line 40
  3. Very specific:

    Do not run pnpm --filter @copilotkit/web-inspector run dev.

    line 44
  4. Very specific:

    If the change adds, renames, or removes a pane, load inspector-docs too.

    line 51
  5. Very specific:

    Wait until http://127.0.0.1:5177 serves.

    line 53
  6. Distinctive:

    If the bug is an empty, locked, error, or unread state, pick that scenario in the lab dropdown, then reload.

    line 56
  7. Distinctive:

    Wait until the overlay is open on Home or Threads.

    line 57
  8. Distinctive:

    Wait for Vite to reload the lab.

    line 63
  9. Distinctive:

    If the page did not pick up the change, reload the lab URL, then wait for the overlay.

    line 64
  10. Very specific:

    If the browser tool writes a file, write it under .inspector-workbench/<task>/.

    line 66
  11. Distinctive:

    Look at the screenshot. If the change is not visible, the work is not done.

    line 67
  12. Distinctive:

    If layout or the collapsed rail is in scope, take a second screenshot at a narrow viewport.

    line 69
  13. Distinctive:

    If theme or contrast is in scope, take light and dark screenshots.

    line 70
  14. Very specific:

    After the Inspector task is done, stop the dev:standalone process tree.

    line 76
  15. Distinctive:

    Do not leave Vite or the CSS watch running.

    line 77
  16. Very specific:

    Do not commit files under .inspector-workbench/.

    line 78
  17. Distinctive:

    Do not commit PNG files at the repo root.

    line 79
  18. Distinctive:

    After the task: Procedure 3

    line 86
  19. Very specific:

    If a pane is added, renamed, or removed: also load inspector-docs

    line 87
  20. Very specific:

    Port 5177 is in use: stop the leftover Inspector workbench on that port, then retry Procedure 1.

    line 107
  21. Distinctive:

    Lab is blank or the overlay is closed: wait for boot. Then screenshot the lab console Runtime line.

    line 109
  22. Distinctive:

    Screenshot does not show the intended change: do not claim done. Reload, screenshot again, then fix the source.

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Inspector Workbench

The Inspector overlay is a visual product. Code that compiles is not proof. The agent must run the standalone workbench and look at screenshots after each visual change.

This skill does not replace inspector-docs. If a pane is added, renamed, or removed, load inspector-docs as well.

When To Use

Load this skill at the start of any task that changes packages/web-inspector UI, chrome, or overlay behavior.

Do not load it for docs-only Callout work. Do not load it for showcase cells. If the host app is the bug (z-index against host CSS, CopilotChat layout), use that host, then still take screenshots.

Default host

The default host is the standalone Threads state lab:

  • Command, from the repo root: nx run @copilotkit/web-inspector:dev:standalone
  • URL: http://127.0.0.1:5177/?scenario=pro-enabled-existing&reset=1
  • The lab mounts the real cpk-web-inspector and opens the overlay.

Do not start a showcase app, an example app, or Storybook as the default host. Those are slower and hide Inspector-only faults.

The Nx target runs Vite and the CSS watch together. Do not run Vite alone. Do not run pnpm --filter @copilotkit/web-inspector run dev. That watch serves consumers, not this lab.

Procedures

Procedure 1: Start the workbench

  1. If the change adds, renames, or removes a pane, load inspector-docs too.
  2. From the repo root, start nx run @copilotkit/web-inspector:dev:standalone.
  3. Wait until http://127.0.0.1:5177 serves.
  4. Open the browser tool this session has (Playwright MCP, Claude browser, or Codex computer use).
  5. Go to http://127.0.0.1:5177/?scenario=pro-enabled-existing&reset=1.
  6. If the bug is an empty, locked, error, or unread state, pick that scenario in the lab dropdown, then reload.
  7. Wait until the overlay is open on Home or Threads. The lab clicks the launcher.
  8. Take a baseline screenshot. Look at it before any edit.

Procedure 2: Edit, screenshot, look

  1. Edit Inspector source under packages/web-inspector/src.
  2. Wait for Vite to reload the lab.
  3. If the page did not pick up the change, reload the lab URL, then wait for the overlay.
  4. Take a screenshot of the pane that must change.
  5. If the browser tool writes a file, write it under .inspector-workbench/<task>/. Never write a PNG at the repo root.
  6. Look at the screenshot. If the change is not visible, the work is not done.
  7. Repeat steps 1–6 after every visual change.
  8. If layout or the collapsed rail is in scope, take a second screenshot at a narrow viewport.
  9. If theme or contrast is in scope, take light and dark screenshots.

Unit tests still belong in the same change. Screenshots do not replace tests.

Procedure 3: Stop the workbench

  1. After the Inspector task is done, stop the dev:standalone process tree.
  2. Do not leave Vite or the CSS watch running.
  3. Do not commit files under .inspector-workbench/.
  4. Do not commit PNG files at the repo root.

Decision Tree

  • Inspector UI, chrome, overlay, launcher, or pane visuals:
    • Start: Procedure 1
    • While editing: Procedure 2
    • After the task: Procedure 3
    • If a pane is added, renamed, or removed: also load inspector-docs
  • Docs Callout only: stop. Load inspector-docs instead.
  • Bug exists only inside a host app: use that host, then still follow Procedure 2 screenshots.
  • Runtime or core change with no Inspector UI: this skill does not apply.

Red Flags

SignalWhat it meansDo instead
Showcase, example, or Storybook is the first serverThe agent skipped the workbenchStop that server. Run Procedure 1
No screenshot after a visual editThe agent is guessing from CSSTake a screenshot. Look at it
PNG files at the repo root (inspector-open.png)The screenshot path is wrongWrite under .inspector-workbench/<task>/
"The CSS looks correct, so the UI is done"Overlay bugs do not show in sourceScreenshot the lab. Fix what the image shows
Vite started without the Nx targetCSS watch is missingUse nx run @copilotkit/web-inspector:dev:standalone
Port 5178 or a random portThe lab pins 5177Free 5177. Do not pick another port
Workbench still running after the taskWatchers leak memory on this machineRun Procedure 3
Pane added with no inspector-docs passDocs Callout will driftLoad inspector-docs in the same change

Error Handling

  • Port 5177 is in use: stop the leftover Inspector workbench on that port, then retry Procedure 1. Do not pick another port. The lab uses strictPort.
  • No browser tool in this session: tell the user the session cannot see Inspector. Do not guess visual results from CSS or unit tests alone.
  • Lab is blank or the overlay is closed: wait for boot. Then screenshot the lab console Runtime line. If Runtime is not connected, fix the lab before UI edits.
  • Screenshot does not show the intended change: do not claim done. Reload, screenshot again, then fix the source.
  • HMR did not apply a source edit: reload http://127.0.0.1:5177 with the same scenario query. Then screenshot.
  • Need a closed launcher or unread halo: open http://127.0.0.1:5177/?scenario=pro-enabled-existing&replay-notification=1.
  • Any unexpected error: halt and surface the raw error. Do not switch to a showcase app to work around the lab.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.