Getting Started¶
This page covers the intended setup flow for creating a new project from the template.
Choose a Creation Method¶
Use one of these three approaches:
- Use GitHub's Use this template button.
- Use GitHub's import-repository flow with
https://github.com/zenless-lab/python-helloworld.gitif you do not want the generated-from marker. - Clone the repository, remove
.git/, and initialize a new Git repository yourself.
Reinitialize the Project¶
After the new repository exists, remove the template package and project metadata so uv can generate the project shape you actually want:
Replace --lib with --package or --app if that better matches your target.
Restore the Template Tooling¶
Install the development dependencies that this template expects:
Then append the template configuration and remove the template file:
Install Dependencies and Hooks¶
Once the project metadata is in place, install the environment and Git hooks:
These steps align the local environment with the repository configuration and enable automated checks before commits.
Install Default Skills¶
This template no longer stores preset skills directly in the repository. On first setup, install the default skill set with:
pnpm dlx skills add zenless-lab/skills --skill python-docstring-expert --skill python-comment-expert --skill google-docstring-crafter --skill secret-scanner --skill skill-crafter --skill agents-md-crafter --skill readme-crafter --skill conventional-commits
This command means:
pnpm dlxdownloads and runs theskillsCLI without a permanent global install.skills addinstalls skills into the current repository's agent workspace.zenless-lab/skillsis the source repository for the published skills.- Each
--skill ...flag picks one default skill to install.
The development environment includes Node.js so this command can run directly in the dev container. For more skills beyond the default set, check the zenless-lab/skills repository and install the ones that fit your workflow.
Replace Placeholder Content¶
This repository intentionally keeps the example implementation very small. Before starting real work, review and replace:
src/with your real package or app modulestests/with tests that match the new behaviordocs/with project-specific documentationzensical.tomlwith your actual documentation site metadata
Recommended First Checks¶
After setup, run the standard local checks once:
If these commands pass, the template has been reinitialized correctly for normal development.