How to use the Feature Naming Generator.
A feature name should make sense alongside existing terminology. Prefer a clear action or concept over a clever label that needs explanation.
Make the workflow fit your task.
Choose a name that communicates the feature's action or concept within the product's existing vocabulary. Test it in the actual label position and compare nearby features for ambiguity or inconsistent terminology.
- What you provide
- Capability, audience and existing terminology.
- What you get
- Clear consistent feature-name options.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Feature identifies differences between two catalog versions.
Completed example
Consider Compare catalogs or Review changes, depending on whether the label starts the comparison or opens its results.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a feature name always be clever or distinctive?
Clarity may matter more for a control or workflow label. Use distinctive branding only when it does not obscure what the feature does.
Why does the same name imply different actions on different screens?
Separate initiating an operation from viewing its result. Compare labels in context and name the actual action at each point.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑