Sharing this now because I think folks might be interested! I've made a small library for best-effort conversion between lexicon revisions. Introducing lexshift: screen.studio/share/EnqCa4e1 (1 / 3 🧵) #atproto #atdevs
Lexshift Demo — Screen Studio
screen.studioMay 12, 2026 at 8:15 PM
Transmogrify Record - Lexicon Garden
Transform records between ATProtocol lexicon schemas
atproto made simple: publishing lexicons - underreacted
atproto made simple: publishing lexicons - underreacted
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
Standard.site: the Publishing Gateway
Another deep exploration into ATProto and implementing lexicons
GitHub - FujoWebDev/lexicon-guestbook: A lexicon for guestbooks on ATproto
A lexicon for guestbooks on ATproto. Contribute to FujoWebDev/lexicon-guestbook development by creating an account on GitHub.
Rethinking the TypeScript Lexicon tooling - Matthieu's Leaflet
The official Lexicon code generation tooling hasn't evolved much since its initial release. While it serves the core atproto codebase well, third-party developers face significant challenges with bundle size, manual maintenance, and architectural constraints that make building production-ready applications unnecessarily difficult.
New Build Notes article discussing ATProto and how we as developers can go about forming standard lexicons for common datatypes without being overly prescriptive on implementation details that would limit creativity and competition blog.stygiantech.dev/a/3msmoumcr4d23-atproto-stand…
ATProto Standards Bodies—Guiding the Future of the Network
blog.stygiantech.devHey @danabra.mov, I’m working on a new labeler for arbitrary atproto records. I’d like lexicon owners to be able to suggest how to render their lexicons in the app. I’m thinking maybe @inlay.at components as sidecars?
Trezy
I'm working on a new labeler software (i.e. an alternative to Ozone) and this really feels like the right way for these things to work. 😎 #atproto
#atproto is there anything we can do to solve the issues plaguing the lexicon specification right now I don't think it's good that the reference TS and Go SDK do not agree with each other on how lexicons should be interpreted
Ricardo J. Méndez
Hmm. That's generated with prototypey and goat lex lint didn't complain, but I'll look into it, thanks.
