poetry-packaging
Master Python package management with Poetry, dependency resolution, publishing, and project structure
Master Python package management with Poetry, dependency resolution, publishing, and project structure
Increment agent version in pyproject.toml. Use when releasing new versions, updating semantic version, or preparing for deployment.
Publish @autumnsgrove/groveengine to npm with proper registry swap workflow. Use when releasing a new version of the engine package to npm.
Create and deploy new versions to Homebrew tap with automatic cask updates
Guidance for developing under a projects managed by pixi. Always use when workspace managed by pixi (have pixi.toml or pixi.lock in root directory.) Covers all you should know while developing under a pixi-based project: pixi environment commands (install, run, shell, add, task), multi-environment management (-e flag, features), task configuration in pixi.toml, dependencies (conda vs PyPI), lock files, and development workflows. Helps with environment setup, package management, running tasks, debugging pixi.toml errors, and production deployment patterns.
SEMO npm 패키지 배포. Use when (1) "npm 배포", "패키지 배포해줘", (2) CLI/MCP 변경 후 배포, (3) "버전 올리고 배포".
Vet new package dependencies before installation. Triggers when adding packages via pip, npm, yarn, or similar package managers. Checks for typosquatting, known vulnerabilities, low adoption (potential supply chain risk), and package metadata anomalies. Use when: - User asks to install a new package - pip install, npm install, yarn add commands detected - requirements.txt or package.json modifications - User asks "is this package safe?" Blocks: Typosquats, critical vulnerabilities Warns: Low adoption, suspicious metadata
Initialize Rust projects with proper structure, essential crates, and Cargo.toml configuration. Use when starting new Rust binaries or libraries.
Runs Python scripts and manages projects using uv. Use when asked to run a python script, execute python code, run pytest, or install packages. Always uses uv instead of pip or bare python.
C#-specific library development patterns. Use when creating .NET class libraries, designing NuGet packages, configuring project files, implementing strong naming and versioning, writing XML documentation, unit testing with xUnit/NUnit, source generators, and multi-targeting. Extends meta-library-dev with .NET tooling and ecosystem patterns.
Use when developing TypeScript npm packages including tsconfig, package.json exports, dual CJS/ESM builds, and publishing
Create Python projects with modern best practices. Use when asked to create a Python project, FastAPI app, CLI tool, or Python package. Includes uv for package management, Docker, pre-commit, ruff, FastAPI with uvloop, Typer CLI, SQLModel, and Pydantic.
Set up a modern Python project with uv, pyproject.toml, and ruff. Use when creating a new Python project, package, or CLI tool.
Calculate semantic version bumps for any project type using version file adapters
Run Python scripts with inline dependencies using uv and PEP 723.
JavaScript project structure, package.json configuration, dependency management, and Maven integration standards for consistent project setup and builds
Quick reference for uv (fast Python package manager) operations to save tokens. Use when creating virtual environments, installing packages, managing dependencies, or when user asks about uv commands. Provides concise patterns for Python project setup and package management.
Manage Python dependencies using uv package manager. Use when installing, adding, removing, or updating packages. Always prefer uv over pip.