project-init
Interactive project initialization with git setup, workflows, hooks, and build configuration.Triggers: project setup, initialization, scaffold, bootstrap, new projectUse when: starting new projects or initializing repositories
When & Why to Use This Skill
This Claude skill automates the end-to-end initialization of software projects, providing an interactive workflow to set up Git repositories, CI/CD workflows, pre-commit hooks, and build configurations for Python, Rust, and TypeScript. It streamlines the bootstrapping process, ensuring every new project adheres to industry best practices and consistent organizational standards from day one.
Use Cases
- 1. Rapid Project Bootstrapping: Instantly create a production-ready project structure for Python, Rust, or TypeScript with all necessary boilerplate and configuration files.
- 2. Automated Infrastructure Setup: Configure Git repositories, GitHub Actions workflows, and Makefiles automatically to reduce manual setup errors and save developer time.
- 3. Standardizing Development Environments: Enforce consistent linting, testing, and pre-commit hooks across a team or organization to maintain high code quality and uniformity.
- 4. Legacy Project Modernization: Transition unstructured or older codebases into professional repositories by applying standardized templates, metadata, and modern build tools.
| name | project-init |
|---|---|
| description | | |
| Triggers | project setup, initialization, scaffold, bootstrap, new project |
| Use when | starting new projects or initializing repositories |
| model | claude-sonnet-4 |
| tools | [Read, Write, Bash, Glob] |
Table of Contents
- Use When
- Workflow
- 1. Detect or Select Language
- 2. Collect Project Metadata
- 3. Review Existing Files
- 4. Render and Apply Templates
- 5. Initialize Git (if needed)
- 6. Verify Setup
- 7. Next Steps
- Error Handling
- Success Criteria
- Examples
- Example 1: New Python Project
Project Initialization Skill
Interactive workflow for initializing new software projects with complete development infrastructure.
Use When
- Starting a new Python, Rust, or TypeScript project
- Need to set up git, GitHub workflows, pre-commit hooks, Makefile
- Want consistent project structure across team
- Converting unstructured project to best practices
Workflow
1. Detect or Select Language
Load Skill(attune:project-init#language-detection)
- Auto-detect from existing files (pyproject.toml, Cargo.toml, package.json)
- If ambiguous or empty directory, ask user to select
- Validate language is supported (python, rust, typescript)
2. Collect Project Metadata
Load Skill(attune:project-init#metadata-collection)
Gather:
- Project name (default: directory name)
- Author name and email
- Project description
- Language-specific settings:
- Python: version (default 3.10)
- Rust: edition (default 2021)
- TypeScript: framework (React, Vue, etc.)
- License type (MIT, Apache, GPL, etc.)
3. Review Existing Files
Check for existing configurations:
ls -la
Verification: Run the command with --help flag to verify availability.
If files exist (Makefile, .gitignore, etc.):
- Show what would be overwritten
- Ask for confirmation or selective overwrite
- Offer merge mode (preserve custom content)
4. Render and Apply Templates
Load Skill(attune:project-init#template-rendering)
Run initialization script:
python3 plugins/attune/scripts/attune_init.py \
--lang {{LANGUAGE}} \
--name {{PROJECT_NAME}} \
--author {{AUTHOR}} \
--email {{EMAIL}} \
--python-version {{PYTHON_VERSION}} \
--description {{DESCRIPTION}} \
--path .
Verification: Run the command with --help flag to verify availability.
5. Initialize Git (if needed)
# Check if git is initialized
if [ ! -d .git ]; then
git init
echo "Git repository initialized"
fi
Verification: Run git status to confirm working tree state.
6. Verify Setup
Validate setup:
# Check Makefile targets
make help
# List created files
git status
Verification: Run git status to confirm working tree state.
7. Next Steps
Advise user to:
# Install dependencies and hooks
make dev-setup
# Run tests to verify setup
make test
# See all available commands
make help
Verification: Run pytest -v to verify tests pass.
Error Handling
- Language detection fails: Ask user to specify
--lang - Script not found: Guide to plugin installation location
- Permission denied: Suggest
chmod +xon scripts - Git conflicts: Offer to stash or commit existing work
Success Criteria
- All template files created successfully
- No overwrites without user confirmation
- Git repository initialized
make helpshows available targetsmake testruns without errors (even if no tests yet)
Examples
Example 1: New Python Project
**Verification:** Run `pytest -v` to verify tests pass.
User: /attune:init
## Troubleshooting
### Common Issues
**Command not found**
Ensure all dependencies are installed and in PATH
**Permission errors**
Check file permissions and run with appropriate privileges
**Unexpected behavior**
Enable verbose logging with `--verbose` flag