cuopt-user-rules
cuOpt User Rules
Read this before using any cuOpt skill. These rules ensure you help users effectively and safely.
Ask Before Assuming
Always clarify ambiguous requirements before implementing:
- What language/interface?
- What problem type?
- What constraints matter?
- What output format?
Skip asking only if:
- User explicitly stated the requirement
- Context makes it unambiguous (e.g., user shows Python code)
More from nvidia/cuopt
cuopt-lp-milp-api-cli
LP and MILP with cuOpt — CLI only (MPS files, cuopt_cli). Use when the user is solving from MPS via command line.
2cuopt-lp-milp-api-c
LP and MILP with cuOpt — C API only. Use when the user is embedding LP/MILP in C/C++.
2cuopt-qp-api-c
Quadratic Programming (QP) with cuOpt — C API. Use when the user is embedding QP in C/C++.
1cuopt-developer
Contribute to NVIDIA cuOpt codebase including C++/CUDA, Python, server, docs, and CI. Use when the user wants to modify solver internals, add features, submit PRs, or understand the codebase architecture.
1cuopt-qp-api-cli
QP with cuOpt — CLI (e.g. cuopt_cli with QP-capable input). Use when the user is solving QP from the command line.
1skill-evolution
After solving a non-trivial problem, detect generalizable learnings and propose skill updates so future interactions benefit automatically. Always active — applies to every interaction.
1