Agent skill
setup-skill
Initialize Python project structure with proper directory layout, configuration files, and best practices. Use when creating new projects or restructuring existing ones.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/setup-skill
SKILL.md
Setup Skill
Purpose
Create and configure Python project structures following modern best practices.
Instructions
-
Create Directory Structure
bashmkdir -p src/package_name/{models,database,services,ui,utils} mkdir -p tests touch src/package_name/__init__.py touch src/package_name/main.py -
Create pyproject.toml
toml[project] name = "project-name" version = "0.1.0" description = "Project description" requires-python = ">=3.11" dependencies = [] [project.scripts] app = "package_name.main:app" [build-system] requires = ["hatchling"] build-backend = "hatchling.build" -
Create .gitignore
__pycache__/ *.py[cod] .venv/ .env *.json !package.json .pytest_cache/ .coverage htmlcov/ dist/ build/ *.egg-info/ -
Create README.md
markdown# Project Name ## Installation ```bash uv syncUsage
bashuv run app
Examples
Create a new todo app structure
mkdir -p retro_todo/{models,database,services,ui,utils}
mkdir -p tests
touch retro_todo/__init__.py
touch retro_todo/main.py
Best Practices
- Use
srclayout for packages that will be distributed - Keep flat layout for internal tools
- Always include
__init__.pyfiles - Create separate directories for different concerns
- Include proper configuration files from start
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?