Use folders when you want to browse a known area of work. Use search when you remember the job, phrase, or outcome but not where the prompt lives. Most growing prompt libraries need both, with fewer folders than their owners first expect.
The right retrieval method is the one that gets you to a recognizable result without forcing you to remember the system perfectly.
Folders provide orientation
Folders answer “what kind of work is this?” A small set such as development, research, operations, planning, and writing gives the library a visible shape.
Browsing works well when:
- you know the category
- the collection is still small
- nearby prompts help you compare options
- you are reviewing everything in one workflow
Folders become a problem when they require several decisions before you reach a file. If you regularly wonder whether a prompt belongs under marketing/content/writing or operations/comms/templates, the structure is asking too much.
Search provides recall
Search answers “what was the prompt supposed to do?” It is faster when titles and descriptions use the words you naturally remember.
Search works well when:
- the library spans several categories
- prompts can belong to more than one workflow
- you remember an outcome but not a path
- keyboard retrieval is part of the routine
Search cannot rescue vague metadata. Files named prompt-12 and final-version remain hard to recognize even when the search engine finds them.
Compare the failure modes
| Method | Works when | Fails when |
|---|---|---|
| Folders | categories are broad and stable | nesting becomes deep or ambiguous |
| Search | titles and descriptions match remembered tasks | naming is vague or results look identical |
The failure of one method often points to a metadata problem rather than a need for more software.
Build a simple hybrid
Start with no more than five to seven top-level folders. Name each prompt by outcome and add a one-sentence description.
Then use this rule:
- Browse when reviewing a whole category.
- Search when trying to run one prompt now.
- Add a folder only when several prompts share a stable workflow.
- Fix titles before adding deeper nesting.
This keeps the folder tree understandable while letting search handle cross-cutting tasks.
Test retrieval instead of debating taxonomy
Choose ten prompts and write down the phrase you would use to find each one a month later. Ask someone else to do the same if the library is shared.
Search those phrases. If the right file does not appear or cannot be recognized, improve the title and description. If several unrelated files appear, narrow the task language.
The test measures actual recall rather than whether the folder tree looks tidy.
How Promptlight handles retrieval
Promptlight indexes Markdown files in a local vault and provides keyboard search, favorites, and a quick copy flow. Your folder structure remains visible in the underlying files, and Finder reveal gives you direct access when you want to browse or edit outside the app.
It does not assign folders or write descriptions automatically. The best results still come from clear names and a structure that reflects real work.
See Prompt Search for Mac and Mac Prompt Launcher for the retrieval workflow, or use Name, Tag, and Search Prompts Consistently to improve the source metadata.
