Larger pieces that ship as Go modules from grit-plugins. Installed with go get rather than grit plugin add, because they are libraries your code imports rather than code generated into it.

websockets

Realtime hub with rooms, presence and typing indicators

notifications

In-app and push notifications with a delivery log

search

Full-text search across resources

stripe

Subscriptions and recurring billing

oauth

i18n

Translated API messages and locale negotiation

video

Video upload, transcode and playback

export

Scheduled exports to CSV and XLSX

conference

Audio and video rooms

go get github.com/MUKE-coder/grit-plugins/grit-websockets

Community

Written by other people and listed here on request.

Listing is not endorsement

The review is deliberately shallow: that the repository exists, that it installs and removes cleanly on a fresh project, and that it is not obviously hostile. Nobody audits the code for you. A plugin writes files into your project and patches existing ones, so read what it did with git diff, the same as any dependency.

Nothing listed yet

If you have written one, yours can be the first. Submission is three commands and a GitHub issue.

Write a plugin

Installing one takes the repository directly. Grit names the source and confirms before cloning, and nothing from the repository is executed: it reads the manifest and writes the files that manifest names.

grit plugin add github.com/someone/grit-calendar

Listing your own

grit plugin submit prints the checklist and the submission link. Three commands on a freshly scaffolded project, and the third is the one people skip:

grit plugin add <your repo>installs without errors
go build ./...compiles afterwards
grit plugin remove <name>leaves the project compiling again

Removal replays the lockfile backwards, so it only works if every change the plugin made is one the lockfile recorded. A plugin that edits a file outside the injection mechanism installs fine and leaves wreckage when it is taken out.