Generate Makefile.local with local development targets for Python projects. Supports configurable venv location (project-local .venv recommended, or centralized ~/.venvs/).
Generates a standardized Makefile.local with development targets for Python projects, configuring virtual environment location and project setup.
npx claudepluginhub jugrajsingh/skillgardenThis skill is limited to using the following tools:
references/centralized.makefile.mdreferences/project-local.makefile.mdGenerate Makefile.local with local development targets. This file stores project-specific configuration (venv location, PYTHONPATH) and provides standardized commands.
.venv/ recommended - Standard convention, IDE-friendlyuv run or uv syncmake -f Makefile.local help shows all targetsTemplates are in references/ folder:
references/project-local.makefile.md - For .venv/ (recommended)references/centralized.makefile.md - For ~/.venvs/{project}/basename $(pwd)
Use for default venv name and project identification.
Present via AskUserQuestion with .venv/ as recommended (first option):
question: "Where should the virtual environment be created?"
header: "Venv location"
options:
- label: ".venv/ (Recommended)"
description: "IDE auto-detects, standard uv convention, isolated per checkout"
- label: "~/.venvs/{project_name}/"
description: "Clean project directory, survives git clean, shared across worktrees"
Glob: Makefile.local
If exists, ask via AskUserQuestion:
Based on user's venv choice:
For .venv/ (recommended):
Read: references/project-local.makefile.md
For ~/.venvs/:
Read: references/centralized.makefile.md
Extract the makefile content from the markdown code block.
For project-local (.venv/):
For centralized (~/.venvs/):
{project_name} with actual project nameWrite to Makefile.local.
Created Makefile.local:
Configuration:
- Venv: {venv_location}
- PYTHONPATH: exported (enables bare imports)
Targets:
setup-local - Full local setup (deps + hooks)
install-dev - Install all dependencies
test - Run tests
lint - Run linter
format - Format code
type-check - Run type checker
quality - Run all quality checks
fix - Auto-fix lint + format
clean - Remove caches
reset - Full reset
Usage:
make -f Makefile.local setup-local # First time setup
make -f Makefile.local test # Run tests
make -f Makefile.local quality # Check code
Other skills should use Makefile.local commands:
# Instead of: uv sync
make -f Makefile.local install-dev
# Instead of: uv run pytest
make -f Makefile.local test
# Instead of: uv run ruff check .
make -f Makefile.local lint
This ensures consistent venv location and PYTHONPATH regardless of configuration.
Users can add project-specific targets:
# =============================================================================
# Application
# =============================================================================
.PHONY: run run-dev
run: ## Run the application
uv run python main.py
run-dev: ## Run with auto-reload
uv run python main.py --reload
# =============================================================================
# Infrastructure
# =============================================================================
.PHONY: infra-up infra-down
infra-up: ## Start Docker services
docker compose up -d --wait
infra-down: ## Stop Docker services
docker compose down
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.