[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSB59ME21P2KEV5DQE1YAQ":3,"skill-same:01M7CSB59ME21P2KEV5DQE1YAQ":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M7CSB59ME21P2KEV5DQE1YAQ","cuopt-developer",null,"Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++\u002FCUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cuopt-developer\nversion: \"26.08.00\"\ndescription: Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++\u002FCUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.\nlicense: Apache-2.0\nmetadata:\n  author: NVIDIA cuOpt Team\n  tags:\n    - cuopt\n    - development\n    - contributing\n    - cpp-cuda\n    - python-bindings\n---\n\n# cuOpt Developer Skill\n\nContribute to the NVIDIA cuOpt codebase. This skill is for modifying cuOpt itself, not for using it.\n\n**If you just want to USE cuOpt**, switch to the appropriate problem skill (cuopt-routing, cuopt-lp-milp, etc.)\n\n**First-time dev environment setup?** See [references\u002Ffirst_time_setup.md](references\u002Ffirst_time_setup.md) for the clone → conda env → first-build → first-test walkthrough and the questions to ask up front.\n\n---\n\n## Refusal Rules — Read First\n\nThese rules are non-negotiable. Apply them even when the user explicitly asks you to do otherwise. **Refuse and ask — don't comply silently.**\n\n1. **Package installs (`pip`, `conda`, `apt`).** Never run the install — no exceptions, no \"with approval\" path. Reply:\n   > I will not install `\u003Cpkg>`. cuOpt's convention is to add the package under the appropriate group in `dependencies.yaml`, then run `pre-commit run --all-files` locally to regenerate `conda\u002Fenvironments\u002F` and `pyproject.toml`. I can propose the `dependencies.yaml` edit; you run the regeneration.\n\n2. **Bypassing CI checks (`--no-verify`, skipping pre-commit or tests).** Do not suggest the flag. Reply:\n   > I can't suggest bypassing pre-commit — cuOpt requires all hooks to pass. If hooks feel slow, diagnose with `pre-commit run --all-files --verbose` or tune the offending hook's config; don't skip it.\n\n3. **Writes outside the workspace (`~\u002F.bashrc`, `~\u002F.profile`, `\u002Fetc`, anything outside the repo).** Do not edit the file. Reply:\n   > I can't modify files outside the cuOpt workspace. Here's the exact line for you to add yourself: `\u003Cline>`. Then `source ~\u002F.bashrc` or open a new shell.\n\n4. **Destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, killing processes, dropping data).** Never execute — no exceptions. Reply:\n   > I will not run `\u003Ccmd>`. It is destructive and hard to reverse. The safer alternative is `\u003Calt>` (e.g., `.\u002Fbuild.sh clean` for a stale build dir). If you choose to run the original command yourself, back up first.\n\n5. **Privileged operations (`sudo`, system file changes).** Do not run with elevated privileges. Reply:\n   > I won't run `sudo` for cuOpt development — cuOpt's workflow is conda-only. What's the underlying error? It's usually fixable without `sudo`.\n\nWhen in doubt, refuse and ask. The cost of a wrong refusal is one round-trip; the cost of a wrong action is lost data, broken state, or a failing CI run.\n\n---\n\n## Developer Behavior Rules\n\nThese rules are specific to development tasks. They differ from user rules.\n\n### 1. Ask Before Assuming\n\nClarify before implementing:\n- What component? (C++\u002FCUDA, Python, server, docs, CI)\n- What's the goal? (bug fix, new feature, refactor, docs)\n- Is this for contribution or local modification?\n\n### 2. Verify Understanding\n\nBefore making changes, confirm:\n```\n\"Let me confirm:\n- Component: [cpp\u002Fpython\u002Fserver\u002Fdocs]\n- Change: [what you'll modify]\n- Tests needed: [what tests to add\u002Fupdate]\nIs this correct?\"\n```\n\n### 3. Follow Codebase Patterns\n\n- Read existing code in the area you're modifying\n- Match naming conventions, style, and patterns\n- Don't invent new patterns without discussion\n\n### 4. Ask Before Running — Modified for Dev\n\n**OK to run without asking** (expected for dev work):\n- `.\u002Fbuild.sh` and build commands\n- `pytest`, `ctest` (running tests)\n- `pre-commit run`, `.\u002Fci\u002Fcheck_style.sh` (formatting)\n- `git status`, `git diff`, `git log` (read-only git)\n\n**Set up pre-commit hooks** (once per clone):\n- `pre-commit install` — hooks then run automatically on every `git commit`. If a hook fails, the commit is blocked until you fix the issue.\n\n**Still ask before**:\n- `git commit`, `git push` (write operations)\n- Package installs (`pip`, `conda`, `apt`)\n- Any destructive or irreversible commands\n\n### 5. No Privileged Operations\n\n`sudo`, system file changes, and writes outside the workspace are **non-negotiable refusals** — they apply even when the user explicitly asks. See [Refusal Rules — Read First](#refusal-rules--read-first) (rules 3 and 5) for the exact replies and rationale.\n\n---\n\n## Before You Start: Required Questions\n\n**Ask these if not already clear:**\n\n1. **What are you trying to change?**\n   - Solver algorithm\u002Fperformance?\n   - Python API?\n   - Server endpoints?\n   - Documentation?\n   - CI\u002Fbuild system?\n\n2. **Do you have the development environment set up?**\n   - Built the project successfully?\n   - Ran tests?\n\n3. **Is this for contribution or local modification?**\n   - If contributing: will need to follow DCO signoff\n\n4. **Which branch should this target?**\n   - During development phase: `main`\n   - During burn down: `release\u002FYY.MM` (e.g., `release\u002F26.06`) for the current release, `main` for the next\n   - Check if a release branch exists: `git branch -r | grep release`\n   - For current timelines, see the [RAPIDS Maintainers Docs](https:\u002F\u002Fdocs.rapids.ai\u002Fmaintainers\u002F)\n\n## Project Architecture\n\n```\ncuopt\u002F\n├── cpp\u002F                    # Core C++ engine\n│   ├── include\u002Fcuopt\u002F      # Public C\u002FC++ headers\n│   ├── src\u002F                # Implementation (CUDA kernels)\n│   └── tests\u002F              # C++ unit tests (gtest)\n├── python\u002F\n│   ├── cuopt\u002F              # Python bindings and routing API\n│   ├── cuopt_server\u002F       # REST API server\n│   ├── cuopt_self_hosted\u002F  # Self-hosted deployment\n│   └── libcuopt\u002F           # Python wrapper for C library\n├── ci\u002F                     # CI\u002FCD scripts\n├── docs\u002F                   # Documentation source\n└── datasets\u002F               # Test datasets\n```\n\n## Supported APIs\n\n| API Type | LP | MILP | QP | Routing |\n|----------|:--:|:----:|:--:|:-------:|\n| C API    | ✓  | ✓    | ✓  | ✗       |\n| C++ API  | (internal) | (internal) | (internal) | (internal) |\n| Python   | ✓  | ✓    | ✓  | ✓       |\n| Server   | ✓  | ✓    | ✗  | ✓       |\n\n## Safety Rules (Non-Negotiable)\n\n### Minimal Diffs\n- Change only what's necessary\n- Avoid drive-by refactors\n- No mass reformatting of unrelated code\n\n### No API Invention\n- Don't invent new APIs without discussion\n- Align with existing patterns in `docs\u002Fcuopt\u002Fsource\u002F`\n- Server schemas must match OpenAPI spec\n\n### Don't Bypass CI\n- Never suggest `--no-verify` or skipping checks\n- All PRs must pass CI\n\n### CUDA\u002FGPU Hygiene\n- Keep operations stream-ordered\n- Follow existing RAFT\u002FRMM patterns\n- No raw `new`\u002F`delete` - use RMM allocators\n\n## Build & Test\n\n### Pre-flight Checks (Required Before First Build or Test)\n\nSkipping any of these surfaces as confusing runtime errors later. Run them in order:\n\n1. **Check CUDA driver compatibility.** Run `nvidia-smi` and read the *CUDA Version* in the top-right corner — that's the maximum CUDA your driver supports. Pick a conda env file from `conda\u002Fenvironments\u002Fall_cuda-\u003Cver>_arch-\u003Carch>.yaml` whose CUDA major version is **≤** that. A mismatch builds successfully but fails at runtime inside RMM with `cudaMallocAsync not supported with this CUDA driver\u002Fruntime version` — verify this *before* the build, not after.\n2. **Create and activate the conda env** before *any* build, test, or `pre-commit` command. Tests link against libraries compiled inside that env; a fresh shell without `conda activate \u003Cenv-name>` hits cryptic linker errors.\n3. **Set `PARALLEL_LEVEL`** if RAM is constrained — see [references\u002Fbuild_and_test.md](references\u002Fbuild_and_test.md). The default `$(nproc)` can OOM mid-build because CUDA compilation needs ~4–8 GB per job.\n4. **For tests, fetch datasets first.** cuOpt tests need MPS files not in the repo — follow the dataset download steps in [CONTRIBUTING.md](..\u002F..\u002FCONTRIBUTING.md) (\"Building for development\" section) and export `RAPIDS_DATASET_ROOT_DIR`.\n\n### Quick Reference\n\n```bash\n.\u002Fbuild.sh             # Build everything\n.\u002Fbuild.sh --help      # List components: libcuopt, cuopt, cuopt_server, docs\nctest --test-dir cpp\u002Fbuild              # C++ tests\npytest -v python\u002Fcuopt\u002Fcuopt\u002Ftests      # Python tests\npytest -v python\u002Fcuopt_server\u002Ftests     # Server tests\n```\n\nFor component-specific build commands, run-test detail, and `PARALLEL_LEVEL` configuration, see [references\u002Fbuild_and_test.md](references\u002Fbuild_and_test.md).\n\n#### Download test datasets before running tests\n\ncuOpt tests depend on MPS\u002Fdata files that are not checked into the repo. A\nmissing dataset surfaces as a `MPS_PARSER_ERROR ... Error opening MPS file`\ntest failure at 0ms — it is not a build or logic failure.\n\nBefore running any C++ or Python tests, follow the dataset download and\n`RAPIDS_DATASET_ROOT_DIR` export steps in the repo's `CONTRIBUTING.md`\n(\"Building for development\" section) — that is the canonical list and mapping.\n\nIf a test fails with a missing-file error, run the matching download step from\n`CONTRIBUTING.md` and re-run the test. Do not report missing-dataset failures\nback to the user as the task outcome.\n\n## Python Bindings\n\ncuOpt uses Cython to bridge Python and C++. See [references\u002Fpython_bindings.md](references\u002Fpython_bindings.md) for the full architecture, parameter flow walkthrough, key files, and Cython patterns.\n\n## Contributing — Commits, PRs, Common Tasks\n\nFor pre-commit setup, DCO sign-off (`git commit -s`), the fork-based PR workflow, the draft-PR rule for agents, PR-description rules (keep it short — no \"how it works\" walkthroughs or file tables), script and CI\u002Fworkflow authoring principles (extend existing files before adding new ones; no speculative flags, restated defaults, or silent fallbacks), and step-by-step common-task recipes (adding a solver parameter, dependency, server endpoint, or CUDA kernel), see [references\u002Fcontributing.md](references\u002Fcontributing.md).\n\n## Coding Conventions\n\nFor C++ naming (`snake_case`, `d_`\u002F`h_` prefixes, `_t` suffix), file extensions (`.hpp`\u002F`.cpp`\u002F`.cu`\u002F`.cuh` and which compiler each uses), include order, Python style, error handling (`CUOPT_EXPECTS`, `RAFT_CUDA_TRY`), memory management (RMM patterns, no raw `new`\u002F`delete`), and test-impact rules, see [references\u002Fconventions.md](references\u002Fconventions.md).\n\n## Troubleshooting & CI\n\nFor build\u002Ftest pitfalls (Cython rebuild, OOM, CUDA driver mismatch, missing `nvcc`) and CI failure diagnostics (style checks, DCO failures, dependency drift), see [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md).\n\n## Key Files Reference\n\n| Purpose | Location |\n|---------|----------|\n| Main build script | `build.sh` |\n| Dependencies | `dependencies.yaml` |\n| C++ formatting | `.clang-format` |\n| Conda environments | `conda\u002Fenvironments\u002F` |\n| Test data | `datasets\u002F` |\n| CI scripts | `ci\u002F` |\n\n## Canonical Documentation\n\n- **Contributing\u002Fbuild\u002Ftest**: [CONTRIBUTING.md](..\u002F..\u002FCONTRIBUTING.md)\n- **CI scripts**: [ci\u002FREADME.md](..\u002F..\u002Fci\u002FREADME.md)\n- **Release scripts**: [ci\u002Frelease\u002FREADME.md](..\u002F..\u002Fci\u002Frelease\u002FREADME.md)\n- **Docs build**: [docs\u002Fcuopt\u002FREADME.md](..\u002F..\u002Fdocs\u002Fcuopt\u002FREADME.md)\n- **Python binding architecture**: [references\u002Fpython_bindings.md](references\u002Fpython_bindings.md)\n\n_Shell-execution, install, sudo, and outside-workspace policies are covered by [Refusal Rules — Read First](#refusal-rules--read-first) at the top of this skill._\n\n## VRP dimension internals (routing engine)\n\nWhen implementing or debugging **VRP dimensions** (constraints, objectives, forward\u002Fbackward propagation, `combine`, local-search deltas), read:\n\n- **`references\u002Fvrp_skills.md`** — architecture contracts, required interfaces, and implementation checklist.\n\nRead it **before** adding a new dimension or changing combine semantics.\n\n## Numerical issues in non-routing solver internals\n\nWhen a bug surfaces as **wrong-but-plausible** solver output (invalid lower bound, unexpectedly large duals, 10× iteration blow-up after a small change) rather than a crash, read:\n\n- **`resources\u002Fnumerical_debugging.md`** — methodology for locating catastrophic-cancellation sites, the cancellation patterns endemic to cMIR \u002F flow-cover \u002F MIR-style cut construction, and threshold guidance for numerical guards.\n\nApply the *instrument-first, guard-at-the-exact-site* workflow it describes before patching — speculative fixes on these symptoms usually miss.\n","# cuOpt Developer Skill\n\nContribute to the NVIDIA cuOpt codebase. This skill is for modifying cuOpt itself, not for using it.\n\n**If you just want to USE cuOpt**, switch to the appropriate problem skill (cuopt-routing, cuopt-lp-milp, etc.)\n\n**First-time dev environment setup?** See [references\u002Ffirst_time_setup.md](references\u002Ffirst_time_setup.md) for the clone → conda env → first-build → first-test walkthrough and the questions to ask up front.\n\n---\n\n## Refusal Rules — Read First\n\nThese rules are non-negotiable. Apply them even when the user explicitly asks you to do otherwise. **Refuse and ask — don't comply silently.**\n\n1. **Package installs (`pip`, `conda`, `apt`).** Never run the install — no exceptions, no \"with approval\" path. Reply:\n   > I will not install `\u003Cpkg>`. cuOpt's convention is to add the package under the appropriate group in `dependencies.yaml`, then run `pre-commit run --all-files` locally to regenerate `conda\u002Fenvironments\u002F` and `pyproject.toml`. I can propose the `dependencies.yaml` edit; you run the regeneration.\n\n2. **Bypassing CI checks (`--no-verify`, skipping pre-commit or tests).** Do not suggest the flag. Reply:\n   > I can't suggest bypassing pre-commit — cuOpt requires all hooks to pass. If hooks feel slow, diagnose with `pre-commit run --all-files --verbose` or tune the offending hook's config; don't skip it.\n\n3. **Writes outside the workspace (`~\u002F.bashrc`, `~\u002F.profile`, `\u002Fetc`, anything outside the repo).** Do not edit the file. Reply:\n   > I can't modify files outside the cuOpt workspace. Here's the exact line for you to add yourself: `\u003Cline>`. Then `source ~\u002F.bashrc` or open a new shell.\n\n4. **Destructive commands (`rm -rf`, `git reset --hard`, `git push --force`, killing processes, dropping data).** Never execute — no exceptions. Reply:\n   > I will not run `\u003Ccmd>`. It is destructive and hard to reverse. The safer alternative is `\u003Calt>` (e.g., `.\u002Fbuild.sh clean` for a stale build dir). If you choose to run the original command yourself, back up first.\n\n5. **Privileged operations (`sudo`, system file changes).** Do not run with elevated privileges. Reply:\n   > I won't run `sudo` for cuOpt development — cuOpt's workflow is conda-only. What's the underlying error? It's usually fixable without `sudo`.\n\nWhen in doubt, refuse and ask. The cost of a wrong refusal is one round-trip; the cost of a wrong action is lost data, broken state, or a failing CI run.\n\n---\n\n## Developer Behavior Rules\n\nThese rules are specific to development tasks. They differ from user rules.\n\n### 1. Ask Before Assuming\n\nClarify before implementing:\n- What component? (C++\u002FCUDA, Python, server, docs, CI)\n- What's the goal? (bug fix, new feature, refactor, docs)\n- Is this for contribution or local modification?\n\n### 2. Verify Understanding\n\nBefore making changes, confirm:\n```\n\"Let me confirm:\n- Component: [cpp\u002Fpython\u002Fserver\u002Fdocs]\n- Change: [what you'll modify]\n- Tests needed: [what tests to add\u002Fupdate]\nIs this correct?\"\n```\n\n### 3. Follow Codebase Patterns\n\n- Read existing code in the area you're modifying\n- Match naming conventions, style, and patterns\n- Don't invent new patterns without discussion\n\n### 4. Ask Before Running — Modified for Dev\n\n**OK to run without asking** (expected for dev work):\n- `.\u002Fbuild.sh` and build commands\n- `pytest`, `ctest` (running tests)\n- `pre-commit run`, `.\u002Fci\u002Fcheck_style.sh` (formatting)\n- `git status`, `git diff`, `git log` (read-only git)\n\n**Set up pre-commit hooks** (once per clone):\n- `pre-commit install` — hooks then run automatically on every `git commit`. If a hook fails, the commit is blocked until you fix the issue.\n\n**Still ask before**:\n- `git commit`, `git push` (write operations)\n- Package installs (`pip`, `conda`, `apt`)\n- Any destructive or irreversible commands\n\n### 5. No Privileged Operations\n\n`sudo`, system file changes, and writes outside the workspace are **non-negotiable refusals** — they apply even when the user explicitly asks. See [Refusal Rules — Read First](#refusal-rules--read-first) (rules 3 and 5) for the exact replies and rationale.\n\n---\n\n## Before You Start: Required Questions\n\n**Ask these if not already clear:**\n\n1. **What are you trying to change?**\n   - Solver algorithm\u002Fperformance?\n   - Python API?\n   - Server endpoints?\n   - Documentation?\n   - CI\u002Fbuild system?\n\n2. **Do you have the development environment set up?**\n   - Built the project successfully?\n   - Ran tests?\n\n3. **Is this for contribution or local modification?**\n   - If contributing: will need to follow DCO signoff\n\n4. **Which branch should this target?**\n   - During development phase: `main`\n   - During burn down: `release\u002FYY.MM` (e.g., `release\u002F26.06`) for the current release, `main` for the next\n   - Check if a release branch exists: `git branch -r | grep release`\n   - For current timelines, see the [RAPIDS Maintainers Docs](https:\u002F\u002Fdocs.rapids.ai\u002Fmaintainers\u002F)\n\n## Project Architecture\n\n```\ncuopt\u002F\n├── cpp\u002F                    # Core C++ engine\n│   ├── include\u002Fcuopt\u002F      # Public C\u002FC++ headers\n│   ├── src\u002F                # Implementation (CUDA kernels)\n│   └── tests\u002F              # C++ unit tests (gtest)\n├── python\u002F\n│   ├── cuopt\u002F              # Python bindings and routing API\n│   ├── cuopt_server\u002F       # REST API server\n│   ├── cuopt_self_hosted\u002F  # Self-hosted deployment\n│   └── libcuopt\u002F           # Python wrapper for C library\n├── ci\u002F                     # CI\u002FCD scripts\n├── docs\u002F                   # Documentation source\n└── datasets\u002F               # Test datasets\n```\n\n## Supported APIs\n\n| API Type | LP | MILP | QP | Routing |\n|----------|:--:|:----:|:--:|:-------:|\n| C API    | ✓  | ✓    | ✓  | ✗       |\n| C++ API  | (internal) | (internal) | (internal) | (internal) |\n| Python   | ✓  | ✓    | ✓  | ✓       |\n| Server   | ✓  | ✓    | ✗  | ✓       |\n\n## Safety Rules (Non-Negotiable)\n\n### Minimal Diffs\n- Change only what's necessary\n- Avoid drive-by refactors\n- No mass reformatting of unrelated code\n\n### No API Invention\n- Don't invent new APIs without discussion\n- Align with existing patterns in `docs\u002Fcuopt\u002Fsource\u002F`\n- Server schemas must match OpenAPI spec\n\n### Don't Bypass CI\n- Never suggest `--no-verify` or skipping checks\n- All PRs must pass CI\n\n### CUDA\u002FGPU Hygiene\n- Keep operations stream-ordered\n- Follow existing RAFT\u002FRMM patterns\n- No raw `new`\u002F`delete` - use RMM allocators\n\n## Build & Test\n\n### Pre-flight Checks (Required Before First Build or Test)\n\nSkipping any of these surfaces as confusing runtime errors later. Run them in order:\n\n1. **Check CUDA driver compatibility.** Run `nvidia-smi` and read the *CUDA Version* in the top-right corner — that's the maximum CUDA your driver supports. Pick a conda env file from `conda\u002Fenvironments\u002Fall_cuda-\u003Cver>_arch-\u003Carch>.yaml` whose CUDA major version is **≤** that. A mismatch builds successfully but fails at runtime inside RMM with `cudaMallocAsync not supported with this CUDA driver\u002Fruntime version` — verify this *before* the build, not after.\n2. **Create and activate the conda env** before *any* build, test, or `pre-commit` command. Tests link against libraries compiled inside that env; a fresh shell without `conda activate \u003Cenv-name>` hits cryptic linker errors.\n3. **Set `PARALLEL_LEVEL`** if RAM is constrained — see [references\u002Fbuild_and_test.md](references\u002Fbuild_and_test.md). The default `$(nproc)` can OOM mid-build because CUDA compilation needs ~4–8 GB per job.\n4. **For tests, fetch datasets first.** cuOpt tests need MPS files not in the repo — follow the dataset download steps in [CONTRIBUTING.md](..\u002F..\u002FCONTRIBUTING.md) (\"Building for development\" section) and export `RAPIDS_DATASET_ROOT_DIR`.\n\n### Quick Reference\n\n```bash\n.\u002Fbuild.sh             # Build everything\n.\u002Fbuild.sh --help      # List components: libcuopt, cuopt, cuopt_server, docs\nctest --test-dir cpp\u002Fbuild              # C++ tests\npytest -v python\u002Fcuopt\u002Fcuopt\u002Ftests      # Python tests\npytest -v python\u002Fcuopt_server\u002Ftests     # Server tests\n```\n\nFor component-specific build commands, run-test detail, and `PARALLEL_LEVEL` configuration, see [references\u002Fbuild_and_test.md](references\u002Fbuild_and_test.md).\n\n#### Download test datasets before running tests\n\ncuOpt tests depend on MPS\u002Fdata files that are not checked into the repo. A\nmissing dataset surfaces as a `MPS_PARSER_ERROR ... Error opening MPS file`\ntest failure at 0ms — it is not a build or logic failure.\n\nBefore running any C++ or Python tests, follow the dataset download and\n`RAPIDS_DATASET_ROOT_DIR` export steps in the repo's `CONTRIBUTING.md`\n(\"Building for development\" section) — that is the canonical list and mapping.\n\nIf a test fails with a missing-file error, run the matching download step from\n`CONTRIBUTING.md` and re-run the test. Do not report missing-dataset failures\nback to the user as the task outcome.\n\n## Python Bindings\n\ncuOpt uses Cython to bridge Python and C++. See [references\u002Fpython_bindings.md](references\u002Fpython_bindings.md) for the full architecture, parameter flow walkthrough, key files, and Cython patterns.\n\n## Contributing — Commits, PRs, Common Tasks\n\nFor pre-commit setup, DCO sign-off (`git commit -s`), the fork-based PR workflow, the draft-PR rule for agents, PR-description rules (keep it short — no \"how it works\" walkthroughs or file tables), script and CI\u002Fworkflow authoring principles (extend existing files before adding new ones; no speculative flags, restated defaults, or silent fallbacks), and step-by-step common-task recipes (adding a solver parameter, dependency, server endpoint, or CUDA kernel), see [references\u002Fcontributing.md](references\u002Fcontributing.md).\n\n## Coding Conventions\n\nFor C++ naming (`snake_case`, `d_`\u002F`h_` prefixes, `_t` suffix), file extensions (`.hpp`\u002F`.cpp`\u002F`.cu`\u002F`.cuh` and which compiler each uses), include order, Python style, error handling (`CUOPT_EXPECTS`, `RAFT_CUDA_TRY`), memory management (RMM patterns, no raw `new`\u002F`delete`), and test-impact rules, see [references\u002Fconventions.md](references\u002Fconventions.md).\n\n## Troubleshooting & CI\n\nFor build\u002Ftest pitfalls (Cython rebuild, OOM, CUDA driver mismatch, missing `nvcc`) and CI failure diagnostics (style checks, DCO failures, dependency drift), see [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md).\n\n## Key Files Reference\n\n| Purpose | Location |\n|---------|----------|\n| Main build script | `build.sh` |\n| Dependencies | `dependencies.yaml` |\n| C++ formatting | `.clang-format` |\n| Conda environments | `conda\u002Fenvironments\u002F` |\n| Test data | `datasets\u002F` |\n| CI scripts | `ci\u002F` |\n\n## Canonical Documentation\n\n- **Contributing\u002Fbuild\u002Ftest**: [CONTRIBUTING.md](..\u002F..\u002FCONTRIBUTING.md)\n- **CI scripts**: [ci\u002FREADME.md](..\u002F..\u002Fci\u002FREADME.md)\n- **Release scripts**: [ci\u002Frelease\u002FREADME.md](..\u002F..\u002Fci\u002Frelease\u002FREADME.md)\n- **Docs build**: [docs\u002Fcuopt\u002FREADME.md](..\u002F..\u002Fdocs\u002Fcuopt\u002FREADME.md)\n- **Python binding architecture**: [references\u002Fpython_bindings.md](references\u002Fpython_bindings.md)\n\n_Shell-execution, install, sudo, and outside-workspace policies are covered by [Refusal Rules — Read First](#refusal-rules--read-first) at the top of this skill._\n\n## VRP dimension internals (routing engine)\n\nWhen implementing or debugging **VRP dimensions** (constraints, objectives, forward\u002Fbackward propagation, `combine`, local-search deltas), read:\n\n- **`references\u002Fvrp_skills.md`** — architecture contracts, required interfaces, and implementation checklist.\n\nRead it **before** adding a new dimension or changing combine semantics.\n\n## Numerical issues in non-routing solver internals\n\nWhen a bug surfaces as **wrong-but-plausible** solver output (invalid lower bound, unexpectedly large duals, 10× iteration blow-up after a small change) rather than a crash, read:\n\n- **`resources\u002Fnumerical_debugging.md`** — methodology for locating catastrophic-cancellation sites, the cancellation patterns endemic to cMIR \u002F flow-cover \u002F MIR-style cut construction, and threshold guidance for numerical guards.\n\nApply the *instrument-first, guard-at-the-exact-site* workflow it describes before patching — speculative fixes on these symptoms usually miss.\n",{"name":5,"license":15,"version":24,"metadata":25,"description":7},"26.08.00",{"tags":26,"author":32},[27,28,29,30,31],"cuopt","development","contributing","cpp-cuda","python-bindings","NVIDIA cuOpt Team","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cuopt-developer",{"tool":48,"command":49},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cuopt-developer",{"tool":51,"command":52},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill cuopt-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002FSKILL.md",true,[56,62,66,70,74,78,82,86,90,94,98],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"benchmark\u002Fevals.json","REFERENCE","参考文档",57177,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Fbenchmark\u002Fevals.json",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fbuild_and_test.md",1674,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Fbuild_and_test.md",{"path":67,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcontributing.md",5483,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Fcontributing.md",{"path":71,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fconventions.md",1869,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Fconventions.md",{"path":75,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Ffirst_time_setup.md",2363,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Ffirst_time_setup.md",{"path":79,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fpython_bindings.md",7917,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Fpython_bindings.md",{"path":83,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Ftroubleshooting.md",2411,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Ftroubleshooting.md",{"path":87,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fvrp_skills.md",9004,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Freferences\u002Fvrp_skills.md",{"path":91,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":92,"sourceHtmlUrl":93},"resources\u002Fnumerical_debugging.md",5927,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Fresources\u002Fnumerical_debugging.md",{"path":95,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":96,"sourceHtmlUrl":97},"skill-card.md",2268,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Fskill-card.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"skill.oms.sig","OTHER","其他",6053,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-skills\u002Fskills\u002Fcuopt-developer\u002Fskill.oms.sig",[105,113,120,127,134,141],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]