Skip to content

Preferred libs and tools #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ecoologic wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Preferred libs and tools #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions docs/tools.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# Tools

A list of tools we encourage you to use when you need such functionality.

## Existing tools

1. See [package.json](./../package.json) for tools you might already have at your disposal
2. See [create-t3-turbo](https://github.com/Labrys-Group/create-t3-turbo/blob/main/package.json) if there's a lib that does the job
3. See [our Shadcn common registry](https://github.com/Labrys-Group/common-registry) if there's a lib that does the job
4. See [core library stack](https://www.notion.so/labrys/ee2e6813c3d94cc8ad476c8ecabd09a6?v=7e3f0bfb970941638f9ce6ddffbd36db&source=copy_link)
Copy link
Contributor Author

@ecoologic ecoologic Dec 28, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't want two sources of truth, but I see this project (common-registry) as being central to our development, so I think having the tools here makes sense, and we can move the whole list in here (cleaned up).

In particular, I strongly think GH is collaborative and in Notion it's hard because there's no PR process and it's not how we devs are used to collaborate (we review PRs every day).

But I can accept the status quo, close this PR, and try again eventually when this repo is used on a daily base.

Copy link

@sjustintaylor sjustintaylor Jan 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'd be better if this was here in github. I don't have an issue with it.

Wild idea - do we want to add the whole engineering playbook to a repo?


## Handle server actions in a trpc-like manner

Next safe actions

https://next-safe-action.dev/docs/getting-started

## State management library (signals)

Among other things, avoid creating a provider at the top just to share the same info in two different areas of the UI.

https://github.com/preactjs/signals

## Other and new packages

Should none of the above work, or you have a better idea, please verbalize it in `#dev-team`, so we can decide together if that's the right tool, if it's safe to use, or if we have a better alternative. If accepted, add them [in this file](https://github.com/Labrys-Group/common-registry/blob/main/docs/tools.md).