What problem does it solve?
Building a federated server that speaks ActivityPub involves HTTP Signatures, WebFinger, NodeInfo, JSON-LD vocabularies, delivery queues, and key management. This Skill guides the AI to write correct Fedify-based TypeScript code instead of hand-rolling protocol endpoints or misusing the framework's APIs.
Core Features & Use Cases
- Federation Setup: Configures the
Federation builder pattern, actor/inbox/outbox/collection dispatchers, and inbox listeners with correct URI templates and async semantics.
- Framework Integration: Mounts Fedify through the correct
@fedify/<framework> package for Hono, Express, Next.js, Nuxt, Fastify, Koa, NestJS, Astro, SvelteKit, Fresh, h3, Elysia, or Cloudflare Workers.
- Production Hardening: Covers
KvStore and MessageQueue adapters, key pair management, LogTape logging, OpenTelemetry tracing, the fedify CLI, and a checklist of common mistakes such as missing queues, SSRF guard disabling, and reverse-proxy origin issues.
- Use Case: Ask the AI to scaffold a federated microblog on Hono with Postgres storage, and it will register actor dispatchers, wire inbox listeners for
Follow and Create, and configure a production message queue.
Quick Start
Use the fedify skill to create an ActivityPub server with Hono that exposes an actor, an inbox handling Follow activities, and a Postgres-backed queue.