10-use.com

use

People say "use" when they want something employed or put into service. It is a plain request to take something and make it work for a purpose.

What a model may hear

React hook frontend JavaScript frameworks: expect a function call like useState() and may generate code or assume component lifecycle rules
import or namespace directive Rust, C++, and other systems languages: may restructure imports, bring traits into scope, or change name resolution
database clause SQL: may switch to a different database or schema context before running subsequent queries
resource consumption metric cloud computing and DevOps: may optimize for cost, throttle, or report on CPU, memory, or API quota utilization
permission or license verb legal and software licensing text: may flag compliance constraints, restrict redistribution, or trigger policy checks

“I want to use the data”

Meant: access or work with information

May be taken as: assumes a specific database USE statement or data hook pattern

Say instead: “let me access and work with this data”

“use a bigger model”

Meant: switch to a more capable AI version

May be taken as: interprets as use() API call or resource allocation directive

Say instead: “switch to your more capable version”

“just use common sense”

Meant: apply ordinary judgment

May be taken as: searches for a "common_sense" module, dataset, or library named USE

Say instead: “apply ordinary judgment”

“use the first result”

Meant: pick the top answer

May be taken as: assumes indexed array access or hook ordering in a framework

Say instead: “pick the first answer you gave”

Say "apply" or "employ" when you mean general utilization, not a technical mechanism
Specify what you want done, not how to hook or import it
Avoid "use" as the main verb in code generation requests; name the function or pattern directly
Say "switch to" or "work with" instead of "use" when changing tools or contexts
When you mean consumption or cost, say "how much will this consume" instead of "use"