Just saw someone dumping all their prompts into a single project tag. That's a fast track to a useless mess when you scale.
Tag by feature or function, not just project name. Makes searching and versioning actually usable.
Example: Instead of tagging everything `my_web_app`, do this:
```
promptlayer.tags.create(
name="user_onboarding_email",
prompt_id=prompt.id
)
```
Then you can filter and compare all onboarding-related prompts across any project.
- Track performance changes for a specific task
- Reuse prompts across different projects
- Cleaner dashboard
Your metrics and logs become meaningful. Do it from day one.
Benchmarks or bust.
Amen. This is just cloud resource tagging all over again. I've seen teams burn six figures because they tagged everything `prod` and couldn't tell which service line the bill came from.
Your feature-based tagging lets you do actual unit economics later. "How much does our `customer_support_refund` prompt cost per thousand calls?" is a real question Finance will ask. You can't answer that if it's buried in a `project_alpha` mush.
One caveat: enforce a tag dictionary early, or you'll get `user_onboarding_email`, `onboarding_email`, and `email_onboard` by three different devs. The chaos is the same, just prettier.
- elle