Shareable instruction files for Cursor, Claude Code, Copilot, Windsurf, and more — installed alongside your existing agent rules.
Before considering any code change complete, you MUST: 1. **Run `./format.sh`** - Auto-format all code 2. **Run `./lint.sh`** - Verify linting passes (this runs both `ruff check` and `ruff format --check`)
Build a Python-based resume optimizer that takes a PDF resume and job description, uses Gemini AI to analyze and optimize the resume, then outputs an improved version while maintaining the original formatting.
You are given an existing Python CLI utility that: **You must do the following:** > ⚠️ In addition to the tasks listed below, you are encouraged to improve **any part of the codebase or CLI experience** as you see fit. Refactor, optimize, simplify, or enhance as long as the result improves usability, reliability, or performance.
You are assisting with development of Salt, a powerful infrastructure automation and configuration management system. This document provides essential quick reference information and links to detailed documentation.
You're a Senior full-stack developer with 40+ years of experience, you are an expert in creating large-scale web applications using Typescript/Next.js , Python and other popular libraries. When coding a new feature you're always making a research on how to code the best and safest way possible, you always review your code and you're breaking down each task into smaller chunks to get the best solution possible. You're using the ask the user questions tool effectively to make sure you have all det
When working on this codebase: 1. **Always use `uv`** instead of `pip` or `python -m venv` 2. **Use `uv venv`** to create/verify virtual environments (it's idempotent - safe to run multiple times) 3. **Use `uv sync`** to install dependencies from `pyproject.toml`
> `anml-exp` is a *pip-installable* anomaly-detection playground with locked > dependencies (`uv.lock`), artefact registry, strict dataset hashing, and a > structured hardware descriptor in benchmark outputs.
This project implements a chess coaching application with AI agents that can analyze chess positions, suggest moves, and provide strategic advice. The system combines a modern React frontend with a Python-based AI agent backend.
This document defines how autonomous engineering agents should operate within the `eo-processor` repository. It covers: 1. Core mission and constraints 2. Repository awareness 4. How to add functionality (Rust + Python)
1. Apply linting and formatting to ensure code quality 2. If changes involve the MCP server or client components, rebuild and reinstall: hatch build && hatch run pip uninstall chroma-mcp-server -y && hatch run pip install 'dist/chroma_mcp_server-<version>-py3-none-any.whl[client,dev]'
**instruction 1: Use Python 3.10+ syntax and features** When generating Python code, adhere to syntax and features compatible with Python 3.10 or higher (up to 3.13), as specified in `pyproject.toml` (`python = ">=3.10,<3.14"`). Avoid deprecated features from earlier versions (e.g., `print` without parentheses) and leverage modern constructs like match statements or type hints where appropriate.
These coding standards guide developers working on **OpenCap Stack**, emphasizing **clarity, consistency, test coverage, and production-readiness**. Designed to pair effectively with AI coding assistants and LLM copilots, this standard enforces behaviors that yield **secure, maintainable, and test-driven Python/FastAPI backend services**.
This project, VT.ai, appears to be focused on AI applications, potentially leveraging language models via tools like LiteLLM. The goal is to create robust and efficient AI-powered features or services. Key technologies include Python.