Organize snippets with folders and tags
Folders give the library a stable structure. Tags connect snippets across projects and make them easier to discover through search.
Use folders for broad ownership
Create folders around a durable subject such as a client, role, project, or kind of work. A snippet normally belongs to the folder where you would expect to browse for it.
├── Git
├── Docker
├── Releases
└── Incident response
Use tags for overlapping context
Tags are useful when one snippet belongs to several concepts. A production deployment command might live in Releases while carrying tags such as production, rollback, and ops.
Make search metadata useful
- Name: describe what the snippet produces, not where it was created.
- Description: explain when to use it or what distinguishes it from similar snippets.
- Trigger: keep it short and consistent with the rest of the folder.
- Tags: add only terms you would realistically search for.
- Documentation: attach prerequisites, warnings, links, or context that should travel with the snippet.
Avoid over-organizing
Start with a few broad folders and add structure only when browsing becomes difficult. Too many empty folders and nearly identical tags create more choices without improving retrieval. Global search can cover the remaining ambiguity.
If you can find a snippet by browsing and by searching one remembered word, the organization is working.