Skip to content
Skills Library
Programming · Building & coding

project-init

/project-init

Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.

Licence
MIT
Last repository change
01.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.

Original author description

Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.

How it works

  1. Use When
  2. Workflow
  3. Error Handling
  4. Success Criteria
  5. Exit Criteria
  6. Examples
Original SKILL.md headings · 149 lines, 601 words
SKILL.md preview
---
name: project-init
description: Scaffolds new projects with git, CI/CD workflows, pre-commit hooks, and build config. Use when starting a new Python, Rust, or TypeScript project from scratch.
alwaysApply: false
model: sonnet
tools: []
modules:
- ./modules/language-detection.md
- ./modules/metadata-collection.md
- ./modules/template-rendering.md
model_hint: standard
role: entrypoint
---

# Project Initialization Skill

Interactive workflow for initializing new software projects with complete development infrastructure.

## Use When

- Starting a new Python, Rust, or TypeScript project
- Updating existing project tooling to current standards
- Need to set up git, GitHub workflows, pre-commit hooks, Makefile
- Want consistent project structure across team
- Converting unstructured project to best practices
- Adding missing configurations to established codebases

## Workflow

### 1. Detect or Select Language

Load `modules/language-detection.md`

- 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 `modules/metadata-collection.md`

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:
```bash
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 `modules/template-rendering.md`

Run initialization script:
```bash
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.

The script also scaffolds the project decision journal: `docs/tradeoffs.md`
and `docs/lessons-learned.md`. These are append-only logs that later workflows
(brainstorm, specify, plan, execute, review) write to as decisions and lessons
arise. Existing journal files are never overwritten. The format follows the
`leyline:decision-journal` contract; init uses leyline's template when present
and a vendored copy otherwise, so it works with or without leyline installed.

**Verification:** Confirm `docs/tradeoffs.md` and `docs/lessons-learned.md`
exist and each contains an `## Active index` and an `## Archive` section.

### 5. Initialize Git (if needed)

```bash
# 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:
```bash
# 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:
```bash
# 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 +x` on 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 help` shows available targets
- `make test` runs without errors (even if no tests yet)

## Exit Criteria

- [ ] Template files for the selected language are created (or, in dry-run,
  reported) with no unconfirmed overwrites.
- [ ] `docs/tradeoffs.md` and `docs/lessons-learned.md` exist, each with an
  `## Active index` and an `## Archive` section.
- [ ] A pre-existing journal file is detected and left unmodified.
- [ ] Git is initialized (unless `--no-git`) and `make help` lists targets.
- [ ] Running with `--dry-run` writes no files, including the journal.

## Examples

### Example 1: New Python Project

```
**Verification:** Run `pytest -v` to verify tests pass.
User: /attune:project-init
Files in this package (4)
  • SKILL.md 5 KB
  • modules/language-detection.md 2 KB
  • modules/metadata-collection.md 3 KB
  • modules/template-rendering.md 4 KB

Versions

RepositoryScoreLicence
This page · athola/claude-night-market100MIT
laurigates/claude-plugins100MIT
duc01226/EasyPlatform100MIT
duc01226/EasyPlatform100MIT
alexzio00/sovereign-skills100MIT
claude-world/director-mode-lite100MIT
raddue/crucible100MIT
dollardill/beads-superpowers100MIT
agencia-conversion/agentic-seo-skills100MIT

Database snapshot: 13.11.2026 · package version e7c6b7204361 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96hk
    Use when bootstrapping hk pre-commit hooks for a project.
  • 100configure-pre-commit
    Set up .pre-commit-config.yaml: hooks for the project type at current revs. Use when installing pre-commit in a repo, auditing stale hook revs, or migrating to pre-commit.
  • 100python-scaffold-method
    Generate a fresh project skeleton, tests and lint config included. TRIGGER WHEN: `/daodan:init-project` runs without an application scaffold and the user wants a Python project, or the user asks to start a new Python project, bootstrap FastAPI/Django/CLI/library structure, or…
  • 100python-scaffold-method
    Generate a fresh project skeleton, tests and lint config included. TRIGGER WHEN: `/daodan:init-project` runs without an application scaffold and the user wants a Python project, or the user asks to start a new Python project, bootstrap FastAPI/Django/CLI/library structure, or…
  • 100project-setup
    Set up a new project with standard structure, git, README, CLAUDE.md, and dev server config. Use when starting a new project or bootstrapping a workspace for a new initiative.
  • 100new-project
    Use when the task matches skill: new project scaffold and this skill''s local workflow.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.