fedify

This skill should be used when adding new ActivityPub/JSON-LD vocabulary types to the @fedify/vocab package, defining new YAML vocabulary schema files, or updating existing vocabulary definitions in Fedify. Applies when implementing FEPs, extending ActivityStreams vocabulary, or adding third-party vocab types such as Mastodon extensions, Litepub types, or other fediverse vocabularies.

This skill is utilized when creating a web framework integration package. After examining the given framework, a feasibility assessment is conducted regarding the creation of an integration package. If implementation is feasible, the package is generated; if it is not possible, the rationale is provided to the user.

This skill is utilized when fetching reviews from GitHub pull requests. Get the reviews, organize, and help to resolve them.

This skill is used to create an example application for a web framework integration package and to test it with `mise test:examples`.

Look up a Fediverse Enhancement Proposal (FEP) and explain how to implement it with Fedify. Use when the user asks about a specific FEP by ID (e.g., FEP-8fcf, FEP-1b12) or wants to implement a fediverse standard in their Fedify application.

Help the user migrate Fedify code between versions. Use when the user needs to upgrade their Fedify version, fix breaking-change errors, or update deprecated API usage.

Fetch and explain Fedify documentation on a specific topic. Use when the user asks about Fedify API details, configuration options, or how a specific feature works. Fetches up-to-date docs from fedify.dev.

Guide the user through implementing an ActivityPub actor with Fedify. Use when the user needs to add or configure an actor dispatcher, set up key pairs, configure aliases, or handle actor-related requests.

Use this skill whenever writing JavaScript or TypeScript code that uses Fedify to build an ActivityPub server, handle federation activities, implement fediverse features, or integrate Fedify with a web framework such as Hono, Express, Next.js, Nuxt, Fastify, Koa, NestJS, Astro, SvelteKit, Fresh, h3, Elysia, or Cloudflare Workers. Covers the `Federation` builder pattern, actor/inbox/outbox/collection dispatchers, inbox listeners, vocabulary objects from `@fedify/vocab`, key pair management, HTTP Signatures, Object Integrity Proofs, the `KvStore` and `MessageQueue` interfaces, database adapter packages, structured logging with LogTape, OpenTelemetry tracing, the `fedify` CLI toolchain, and common mistakes. Also apply when the user mentions ActivityPub, federation, fediverse, WebFinger, NodeInfo, FEPs, or Mastodon interoperability, even if they do not name Fedify explicitly.

Help the user set up Fedify inbox listeners for handling incoming ActivityPub activities. Use when the user needs to handle Follow, Like, Announce, Create, Undo, or other activity types delivered to their inbox.

Make a commit in Git with an appropriate commit message for the currently staged changes.

This skill is used to add an integration package to the @fedify/init package so that users can select the new framework via the `fedify init` command, and to test it with `mise test:init`.