agent-skills

Use when running, deploying, configuring, or operating Pubky backend infrastructure rather than building an app: self-hosting a homeserver (Docker, admin API, config.toml, signup/invite tokens, enable/disable users, the homeserver-dashboard, Cloudflare-tunnel exposure, Umbrel vs standalone); operating the Nexus indexer (nexusd api/watcher/db subcommands, Neo4j + Redis, config.toml, the Migration Manager, OpenTelemetry/Signoz); spinning up the full local stack with pubky-docker compose profiles; gating signups with Homegate (SMS/Lightning/IP, PostgreSQL); running self-sovereign DNS (pkdns resolver + DoH, pkarr-relay, the Mainline DHT); or hosting http-relay for store-and-forward/auth flows. Includes operator/admin CLI workflows via pubky-cli. NOT for building apps that consume Pubky (use pubky or pubky-mobile).

Use when building a native mobile app on Pubky for iOS or Android, via React Native (@synonymdev/react-native-pubky) or the UniFFI-generated Swift/Kotlin/Python bindings (pubky-core-ffi). Covers native module install/linking, key generation and recovery files, homeserver signUp/signIn/session lifecycle, pubky:// put/get/list/delete from mobile, the Result/isErr() and [error,data] response contracts, the documented FFI String Contracts (do not change output formats), the MANDATORY Android rustls TLS init at startup before any handshake, and integrating the Pubky Ring authenticator's pubkyauth:// and pubkyring:// deeplink authorization (capabilities, relay+secret, QR/animated-frame input, session revoke). NOT for web/server SDK usage (use pubky) and NOT for operating backend infrastructure (use pubky-infra).

Use when building or debugging an application on Pubky with the web/server SDKs: signing users up to a homeserver, authenticating with keypairs and the pubkyauth flow (capabilities, relays, recovery files, signup tokens, sessions), reading/writing data over pubky:// URLs (put/get/list/delete with pagination), constructing and validating spec-compliant social objects (users, posts, tags, bookmarks, follows, feeds, files) with pubky-app-specs and its Timestamp/Blake3-Hash IDs and canonical /pub/pubky.app paths, or querying the Nexus social-graph REST API. Covers the JavaScript/WASM client (@synonymdev/pubky) and the Rust client (the pubky crate), pubky:// addressing, pkarr identity resolution, error handling, and local pubky-testnet development. NOT for native iOS/Android or React Native apps (use pubky-mobile) and NOT for running or self-hosting homeserver/Nexus/DNS infrastructure (use pubky-infra).