Receber por email
← Voltar para o catálogo

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.

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/add-event-type/svg)](https://www.skillteca.com.br/skills/add-event-type)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Add Event Type

Instructions

  1. Read current event types in frontend/src/App.tsx:
  2. Find the EventType union type definition
  3. Review existing block components (UserMessageBlock, PlanBlock, TodoBlock, etc.)
  1. Define the new event type interface:

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

  1. Add to EventType union:

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

  1. Create a new block component following existing patterns:

``typescript 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> ); } ``

  1. Add case to the feed rendering switch/conditional in the main component
  1. 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
Compartilhar X LinkedIn