Community toolkits
You don’t have to build every toolkit yourself. Someone who has already worked out a good set of tools for, say, a Supabase app or an Astro marketing site can share it, and you can start from theirs in a minute.
Why start from a shared toolkit
Section titled “Why start from a shared toolkit”- Skip the hunting. Someone already picked tools that work well together for that kind of work.
- See what others use. A shared toolkit shows its tools, where they come from, and which coding apps it works with, before you add anything.
- Make it yours. What you add is your own toolkit. Remove what you don’t need, add what’s missing.
Example: starting a Supabase app
Section titled “Example: starting a Supabase app”You’re about to build a web app on Supabase. In Community toolkits, filter by subcategory, sort by Popular, and open a toolkit that fits. Check its tools and that it works with your coding app, choose Use this toolkit, then Follow updates.
It’s now in Toolkits with your others. Pick it for your next launch, or make it your project’s default toolkit.
Follow updates or save a copy
Section titled “Follow updates or save a copy”When you use a shared toolkit, you choose how it relates to the original.
One shared toolkit, two ways to use it
Follow updates
Your toolkit
Takes the update when Sam shares one
Tools you changed stay as you left them
Save a copy
Your toolkit
Stays as it is today. Later updates never change it.
| Choice | Pick it when | What happens later |
|---|---|---|
| Follow updates | You trust the person who shared it and want their improvements. | Your toolkit takes the update when they share one. Tools you changed stay as you left them. |
| Save a copy | You want a fixed starting point to make your own. | You keep the toolkit as it is today, and later updates never change it. |
Following tells you about an update; it never changes your toolkit on its own. Taking an update adds it as another toolkit, so your own edits are never overwritten, and a project’s default stays as it is.
Use a shared toolkit walks through adding one, launching with it, and taking an update.
Share your own toolkit
Section titled “Share your own toolkit”Why: a teammate starting on your project gets your exact tools in one step, and a toolkit you’re proud of can help other people working on the same kind of thing.
How: run csc toolkit share --toolkit <toolkit-id> --subcategory <subcategory> to list it in Community where anyone can find it, or add --link-only instead of --subcategory to get a link for specific people. A link doesn’t appear in Community.
What you share is a copy of your toolkit as it is when you share it. Your later edits stay private until you share an update. Stopping sharing removes the listing or link, but doesn’t delete copies other people already saved.
csc toolkit share tells you if something in your toolkit can’t be shared. Share your toolkit explains who can open it and what it needs.