vibefed

Detects whether a codebase implements the NodeInfo protocol endpoint. NodeInfo is a standard used by Fediverse and federated social network servers to expose metadata about the instance (software name, version, protocols supported, user counts, etc.). Use this skill whenever the user asks whether a repo or codebase supports NodeInfo, has a /.well-known/nodeinfo endpoint, exposes instance metadata, or implements Fediverse server discovery. Also trigger when auditing a codebase for ActivityPub, Diaspora, or federated social networking support, since NodeInfo is a common companion to those protocols.

Detects whether a codebase implements the WebFinger protocol endpoint (RFC 7033). Use this skill whenever the user asks whether a repo, project, or codebase supports WebFinger, has a /.well-known/webfinger endpoint, implements the JRD response format, or handles acct: URI lookups. Also trigger when the user is auditing a codebase for ActivityPub or federated identity support, since WebFinger is a common dependency.

Background knowledge about Activity Intents on the Fediverse, based on FEP-3b86 (DRAFT status). Covers how servers publish machine-readable URL templates via WebFinger for cross-server social interactions (Follow, Like, Announce, Create, etc.), the rel namespace convention (https://w3id.org/fep/3b86/*), RFC 6570 URI Templates with parameter placeholders, the 28 standard activity intents plus the Object intent, the special Create intent for pre-populating new content, workflow callbacks (on-success, on-cancel), the remote server interaction flow, the fallback chain (Activity Intents → oStatus subscribe → hard-coded URLs), security considerations (CSRF, open redirects, interstitial pages), the history from oStatus remote follow through Mastodon's authorize_interaction endpoint, the Twitter Web Intents inspiration, comparison with Fedilinks (FEP-07d7), and implementations across Emissary, Forte, Loops, PieFed, streams, and WordPress. Load when the user asks about implementing remote interaction buttons; cross-server follow/like/share from a remote website; Activity Intents; FEP-3b86; how to publish interaction endpoints via WebFinger; the oStatus subscribe template; Mastodon's authorize_interaction endpoint; how remote follow works; how to let users interact with content using their home server account; or how to add Follow/Like/Share buttons for Fediverse users on a website.

Background knowledge about FEP-82f6 Actor statuses, an ActivityPub extension for short, non-interactable profile status text. Covers the ActorStatus type (content, endTime expiration, attachment for rich metadata like now-playing), actor fields (status for current inlined status, statusHistory collection), activities (Create to set, Remove to clear from profile but keep in history, Delete to remove entirely), the sm: JSON-LD namespace from Smithereen, the 100-character minimum support requirement, the design philosophy of one FEP = one UX pattern with clean compatibility breaks, the Remove vs Delete distinction, why Update is forbidden, why the featured collection is not reused, and the inspiration from early Facebook "is..." statuses, VKontakte taglines, Discord custom statuses, and GitHub profile statuses. Load when the user asks about actor statuses; profile status text; FEP-82f6; how to add a custom status to an ActivityPub actor; short non-interactable profile messages; status expiration; status history; the ActorStatus type; or the Smithereen sm: namespace.

Background knowledge about FEP-67ff FEDERATION.md, the convention for documenting federation behavior in Fediverse projects. Covers the specification requirements (valid Markdown, repository root location), suggested template sections (protocols, FEPs, ActivityPub details), machine-readable discovery via NodeInfo 2.1 software.repository, the companion FEP-c893 (DOAP JSON-LD for automated capability discovery), the origin story (Darius Kazemi's 2020 proposal, WriteFreely as first adopter), the interoperability documentation gap FEDERATION.md solves, real-world examples from Mastodon and WordPress, and the 40+ implementations that have adopted it. Load when the user asks about FEDERATION.md; how to document federation behavior; FEP-67ff; what protocols or FEPs a project supports; how to create interoperability documentation for a Fediverse project; how other projects document their ActivityPub implementation; or machine-readable federation capability discovery with DOAP.