Marketplace add-event-type

Add a new event type to the frontend feed system with corresponding React component. Use when user mentions "new event", "add event type", "event block", "new block type", or wants to display new agent output types.

install

source · Clone the upstream repo

git clone https://github.com/aiskillstore/marketplace

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/applelamps/add-event-type" ~/.claude/skills/aiskillstore-marketplace-add-event-type && rm -rf "$T"

manifest: skills/applelamps/add-event-type/SKILL.md

Add Event Type

Instructions

Read current event types in
```
frontend/src/App.tsx
```
:
- Find the
```
EventType
```
  union type definition
- Review existing block components (UserMessageBlock, PlanBlock, TodoBlock, etc.)

Define the new event type interface:

type NewEventType = {
  type: 'new_type';
  // Add required fields
};

Add to EventType union:

type EventType = UserMessage | Plan | Todo | ... | NewEventType;

Create a new block component following existing patterns:

function NewTypeBlock({ event }: { event: NewEventType }) {
  return (
    <div className="p-3 bg-zinc-800/50 rounded-lg border border-zinc-700/50">
      {/* Render event data */}
    </div>
  );
}

Add case to the feed rendering switch/conditional in the main component
Update WebSocket message handler if backend sends this event type

Examples

"Add a new 'search_result' event type"
"Create a block for displaying errors"
"Add event type for progress updates"

Guardrails

Follow existing naming conventions (PascalCase components, snake_case event types)
Use existing Tailwind classes for consistent styling
Ensure TypeScript types are complete (no
```
any
```
)
Test by sending mock event through WebSocket