Menu
Repository-level view of 8 collected skills across 4 GitHub repositories.
Top repositories by collected skill count, with their share of this creator catalog and occupation spread.
Guide for building downstream applications on top of the @hypercerts-org/lexicon package. Use when creating apps that read/write Hypercerts records on the AT Protocol network.
Create changeset files for user-facing changes. Use when making schema changes, modifying types, or any change that affects package consumers.
Create changeset files for changes to ePDS that affect end users, client app developers, or operators. Use when adding features, changing configuration, altering OAuth flows, or any change a downstream consumer needs to adapt to.
Implement AT Protocol OAuth login against an ePDS instance. Covers two flows — Flow 1 (email-first, hand-rolled PAR/DPoP) and Flow 2 (via @atproto/oauth-client-node, accepting no hint / handle / DID). Use when building passwordless OTP login, configuring client metadata (confidential vs public), or integrating NodeOAuthClient.
Sync Hypercerts SDK with latest lexicons from the develop branch. Use when updating SDK dependencies, comparing lexicon versions, or reconciling changes between SDK and lexicons repository. Always check the CHANGELOG.md and diffs first to see exactly what changed between versions.
Create changeset files for user-facing changes. Use when making API changes, modifying types, adding features, or any change that affects package consumers.
Create changeset files for changes to the group service that affect end users, client app developers, or operators. Use when adding features, changing configuration, altering the XRPC API or RBAC rules, or any change a downstream consumer needs to adapt to.
Build AT Protocol apps that read and write group-owned records through the Certified Group Service (CGS). Use when an app needs shared, role-gated control of a single atproto account — registering or importing a group, adding/removing members, setting roles, creating/updating/deleting records in the group's repo, uploading blobs, querying the audit log, or issuing API keys for a backend daemon. Triggers: "group account", "shared atproto repo", "certified group service", "app.certified.group.*", "atproto-proxy to a group", "X-API-Key cgsk_".