ai_project_template / rules
Cursor rule1 starsChanged 12 months agoMITView on GitHub
CRITICAL: This project uses UV as the standard Python package manager and virtual environment tool. If converting an existing project: Remember: UV is the standard. Both requirements.txt and pyproject.toml must always be in sync.
- Installs packages
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,183 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository40 other files it gives its agents.
- agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/always.mdcCursor rule
- .cursor/rules/atlassian/atlassian_integration.mdcCursor rule
- .cursor/rules/computer_use/computer_use_agent.mdcCursor rule
- .cursor/rules/documentation.mdcCursor rule
- .cursor/rules/fstrent_spec_tasks/claude_code_cli.mdcCursor rule
- .cursor/rules/github/github_integration.mdcCursor rule
- .cursor/rules/powershell.mdcCursor rule
- .cursor/rules/silicon_valley_personality.mdcCursor rule
- .cursor/rules/web_tools/web_tools.mdcCursor rule
- artifacts-builderSkill
- atlassian-integrationSkill
- claude-code-cli-integrationSkill
- computer-use-agentSkill
- deep-researchSkill
- fstrent-code-reviewerSkill
- fstrent-planningSkill
- fstrent-qaSkill
- fstrent-task-managementSkill
- github-integrationSkill
- hanx-database-toolsSkill
- hanx-knowledge-baseSkill
- hanx-mediawikiSkill
- hanx-youtube-researcherSkill
- internal-commsSkill
- mcp-builderSkill
- oracle-apex-developmentSkill
- patent-filing-aiSkill
- Project SetupSkill
- research-methodologySkill
- skill-creatorSkill
- startup-business-formationSkill
- startup-product-developmentSkill
- startup-resource-accessSkill
- startup-vc-fundraisingSkill
- template-skillSkill
- web-toolsSkill
- youtube-rag-storageSkill
- youtube-video-analysisSkill
The file
Show its rules and text
We split this virtual_environments_python.md into the rules it gives an agent
21 rules. About 0 are common, 12 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Always use uv venv to create virtual environments
- Very specific: line 11
Never use python -m venv or virtualenv directly
- Very specific: line 15
Use uv pip install <package> for installing packages
- Very specific: line 16
Use uv pip install -r requirements.txt for bulk installations
- Very specific: line 17
Use uv run python <script> to run Python scripts in the UV environment
- Very specific: line 20
ALWAYS: keep both requirements.txt AND pyproject.toml synchronized
- Distinctive: line 21
When adding a new package, update BOTH files immediately
- Distinctive: line 22
When removing a package, remove from BOTH files
- Distinctive: line 23
Never let these files get out of sync
- Distinctive: line 65
Ensure version matches what's in requirements.txt
- Distinctive: line 68
Check that both files contain the same package versions
- Distinctive: line 69
Commit both files together
- Distinctive: line 111
If converting an existing project:
- Very specific: line 114
Create UV environment: uv venv
- Very specific: line 116
Update pyproject.toml with all dependencies
- Distinctive: line 117
Verify both files are synchronized
- Distinctive: line 118
Document UV usage in project README
- Very specific: line 122
Code Reviews: Check that both requirements.txt and pyproject.toml are updated
- Distinctive: line 123
CI/CD: Add validation to ensure file synchronization
- Distinctive: line 124
Documentation: Always mention UV in setup instructions
- Distinctive: line 125
Consistency: Never mix pip and UV in the same project
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Python Virtual Environment Management
UV Package Manager
CRITICAL: This project uses UV as the standard Python package manager and virtual environment tool.
Core Requirements
- Virtual Environment Creation
- Always use
uv venvto create virtual environments - Never use
python -m venvorvirtualenvdirectly - UV provides faster, more reliable environment management
- Always use
- Package Installation
- Use
uv pip install <package>for installing packages - Use
uv pip install -r requirements.txtfor bulk installations - Use
uv run python <script>to run Python scripts in the UV environment
- Use
- Dependency Management
- ALWAYS keep both
requirements.txtANDpyproject.tomlsynchronized - When adding a new package, update BOTH files immediately
- When removing a package, remove from BOTH files
- Never let these files get out of sync
- ALWAYS keep both
File Synchronization Rules
requirements.txt
# Format: package==version
numpy==1.24.0
pandas==2.0.0
requests==2.31.0pyproject.toml
[project]
name = "project-name"
version = "0.1.0"
dependencies = [
"numpy==1.24.0",
"pandas==2.0.0",
"requests==2.31.0",
]
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"Workflow for Adding Dependencies
- Install the package:
uv pip install <package> - Update requirements.txt:
uv pip freeze > requirements.txt - Update pyproject.toml:
- Manually add the package with version to the
dependenciesarray - Ensure version matches what's in requirements.txt
- Manually add the package with version to the
- Verify synchronization:
- Check that both files contain the same package versions
- Commit both files together
Common UV Commands
# Create virtual environment
uv venv
# Activate environment (Windows)
.venv\Scripts\activate
# Activate environment (Unix/Mac)
source .venv/bin/activate
# Install package
uv pip install <package>
# Install from requirements
uv pip install -r requirements.txt
# Run script in UV environment
uv run python script.py
# Update all packages
uv pip install --upgrade -r requirements.txt
# List installed packages
uv pip list
# Show package info
uv pip show <package>Benefits of UV
- Speed: 10-100x faster than pip for package resolution
- Reliability: Better dependency conflict resolution
- Compatibility: Drop-in replacement for pip
- Modern: Built with Rust for performance and safety
Migration from pip/venv
If converting an existing project:
- Install UV:
pip install uv - Create UV environment:
uv venv - Install existing requirements:
uv pip install -r requirements.txt - Update pyproject.toml with all dependencies
- Verify both files are synchronized
- Document UV usage in project README
Enforcement
- Code Reviews: Check that both requirements.txt and pyproject.toml are updated
- CI/CD: Add validation to ensure file synchronization
- Documentation: Always mention UV in setup instructions
- Consistency: Never mix pip and UV in the same project
Remember: UV is the standard. Both requirements.txt and pyproject.toml must always be in sync.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

