Skip to content
Skills Library
AI & agents · Tool integration

agent-floor-ui

/agent-floor-ui

Use when integrating Agent Floor UI with an AI agent, Claude workflow, VS Code project, or multi-agent factory. Map agent lifecycle events into a live Three.js workspace using the event API or local relay.

Licence
MIT
Last repository change
10.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when integrating Agent Floor UI with an AI agent, Claude workflow, VS Code project, or multi-agent factory. Map agent lifecycle events into a live Three.js workspace using the event API or local relay.

Original author description

Use when integrating Agent Floor UI with an AI agent, Claude workflow, VS Code project, or multi-agent factory. Map agent lifecycle events into a live Three.js workspace using the event API or local relay.

How it works

  1. Scope
  2. Procedure
  3. Embedding
  4. Boundaries
Original SKILL.md headings · 36 lines, 379 words
SKILL.md preview
---
name: agent-floor-ui
description: 'Use when integrating Agent Floor UI with an AI agent, Claude workflow, VS Code project, or multi-agent factory. Map agent lifecycle events into a live Three.js workspace using the event API or local relay.'
---

# Agent Floor UI Integration

## Scope

Connect the host project's actual agent lifecycle to Agent Floor UI. This skill provides integration instructions, not automatic session access or an agent runtime. Do not invent progress, completions, or agent activity.

## Procedure

1. Identify the host's real agent lifecycle callbacks, tool hooks, or event bus. Ask for the host interface if it is unavailable. Do not scrape private conversations or read credentials.
2. Choose a transport: direct `createFloorStore().dispatch` in a JavaScript application, or HTTP events to the local relay from any language. Keep adapter code in the host project.
3. Use a stable ID for every agent and emit `agent.upsert` when it starts or changes status. All fields are required. Follow the [event contract](./events.md).
4. Emit `agent.move` when the agent's work context changes: `desks` for implementation, `meeting` for coordination, `lab` for validation, `lounge` for idle or research. Map teams or pipelines to floors with the optional `floor` field. Include `progress` only when the host reports real progress. Emit `activity` only for real events. Emit `agent.remove` when the agent leaves.
5. Start `npx agent-floor-ui relay` after installing the package. In a source checkout, run `npm run build` first, then `npm run relay`. Connect the UI to `http://127.0.0.1:4310/events`. The relay binds only to localhost. Use `--origin` for a custom frontend origin.
6. Validate with one real lifecycle operation. Confirm the right ID, status, task, and zone appear. Close streams and unmount UI when the host disposes its adapter.

## Embedding

```tsx
import { AgentFloor, createFloorStore } from 'agent-floor-ui';
import 'agent-floor-ui/style.css';

const store = createFloorStore();
// Render <AgentFloor store={store} demo={false} title="My factory" />.
// Dispatch only observed host events to store.dispatch(event).
```

For a non-React mount, use `mountAgentFloor(element, { demo: false })`. It returns `dispatch`, `store`, and `unmount`.

## Boundaries

- Never claim that installing this skill observes VS Code, Copilot, or Claude sessions automatically.
- Do not add a VS Code extension or Claude hooks until the host integration mechanism is known and authorized.
- Keep the relay local. Do not expose it publicly or put secrets or full prompts in activity messages.
- SSE consumes JSON in ordinary `data:` messages. Reject malformed events rather than passing untrusted data into the scene.
- Cross-window integrations must use `connectWindowMessages(store, exactOrigin, trustedWindow)`, never `*`.
Files in this package (2)
  • SKILL.md 3 KB
  • events.md 2 KB

Versions

The database has no other skills named agent-floor-ui.

Database snapshot: 13.11.2026 · package version e3e7b88edf11 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90agent-event-adapters
    Use when integrating GitHub facts, Claude Code or Codex activity, local agent logs, replay, event provenance, bridge services, or event-to-character animations.
  • 100floor
    Open the "studio floor" — every studio employee in its own colour-coded terminal pane (iTerm2 grid on macOS, or tmux anywhere) running `claude --agent game-studio:<role>` and working its queue on the shared board, plus a live board pane. Built for filming. Use for…
  • 86floor
    Open the floor for the AI's curiosity. Use when wrapping or at natural pauses.
  • 100agent-design
    Use when choosing between workflow vs agent patterns, structuring orchestrator/subagent pipelines, or writing a Claude Code agent template.
  • 95agent-development
    This skill should be used when the user asks to "create an agent", "write an agent", "build an agent", or wants to add new agent capabilities to Claude Code.
  • 100custom-agent
    [AI & Tools] Use when creating, verifying, or enhancing Claude Code custom agent files.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.