Encode naming conventions into Avo for Guardrails, Audit and AI suggestions
k
klara@avo.sh
It would be helpful to be able to encode existing naming conventions directly into Avo, so that when people create events and properties they don’t need to reference separate documentation.
Specifically, these conventions can include:
Event names: For example: noun + present tense verb OR past tense verb + noun.
Property naming patterns for booleans vs non-booleans (e.g., boolean properties follow a specific suffix/prefix pattern)
Additional org-specific rules that should be enforced or strongly guided in the UI
Requested capabilities:
Configurable naming rules (first-class, not just hints)
- Define required structure more specifically (e.g. verb tense)
- Set separate conventions for different property types (boolean vs non-boolean, enums, IDs, etc.)
AI awareness of rules
- A way for Avo AI to consume these naming rules so AI-suggested event and property names follow the configured conventions by default
Expected outcomes:
- Reduce reliance on separate “naming convention” docs in practice
- Decrease review overhead from repeatedly correcting the same naming issues
- Make it easier and safer for non-experts to create high-quality, compliant tracking specs.