Home / Cursor rules / Linux Nvidia Cuda Python
Linux Nvidia Cuda Python
Cursor rules for Linux development with NVIDIA CUDA and Python integration.
Cursor rules (.mdc)Public domain (CC0)
–unranked
Install
mkdir -p .cursor/rules && curl -sL https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/b044f956f021b6e8877f16781bcfc466a6a120e9/rules/linux-nvidia-cuda-python-cursorrules-prompt-file.mdc -o .cursor/rules/linux-nvidia-cuda-python.mdcDownloads the file at commit b044f956f021 into .cursor/rules/.
To remove it later:
rm .cursor/rules/linux-nvidia-cuda-python.mdcContext cost: ≈538 tokens when used.
Rules file
--- description: "Cursor rules for Linux development with NVIDIA CUDA and Python integration." globs: **/* alwaysApply: false --- 1. **Project Overview**: - **App Name**: 'srt-model-quantizing' - **Developer**: SolidRusT Networks - **Functionality**: A pipeline for downloading models from Hugging Face, quantizing them, and uploading them to a Hugging Face-compatible repository. - **Design Philosophy**: Focused on simplicity—users should be able to clone the repository, install dependencies, and run the app using Python or Bash with minimal effort. - **Hardware Compatibility**: Supports both Nvidia CUDA and AMD ROCm GPUs, with potential adjustments needed based on specific hardware and drivers. - **Platform**: Intended to run on Linux servers only. 2. **Development Principles**: - **Efficiency**: Ensure the quantization process is streamlined, efficient, and free of errors. - **Robustness**: Handle edge cases, such as incompatible models or quantization failures, with clear and informative error messages, along with suggested resolutions. - **Documentation**: Keep all documentation up to date, including the README.md and any necessary instructions or examples. 3. **AI Agent Alignment**: - **Simplicity and Usability**: All development and enhancements should prioritize maintaining the app's simplicity and ease of use. - **Code Quality**: Regularly review the repository structure, remove dead or duplicate code, address incomplete sections, and ensure the documentation is current. - **Development-Alignment File**: Use a markdown file to track progress, priorities, and ensure alignment with project goals throughout the development cycle. 4. **Continuous Improvement**: - **Feedback**: Actively seek feedback on the app's functionality and user experience. - **Enhancements**: Suggest improvements that could make the app more efficient or user-friendly, ensuring any changes maintain the app's core principles. - **Documentation of Changes**: Clearly document any enhancements, bug fixes, or changes made during development to ensure transparency and maintainability.
Security
Scanned Nov 4, 2026 at commit b044f956f021, with Cisco's open-source skill-scanner.
None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.
A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan