version: "1.0.0" name: zomp-new-repo description: Zomp setup for a new repository or project - first-commit files (.gitattributes, .editorconfig, .gitignore, README), pnpm, the husky pre-commit hook with Prettier and a final-newline check, and shared VS Code tasks, launch and extension recommendations. Load this before creating a repository or its first commit, and before adding hooks, formatting, editor config or .vscode files to an existing repo.

New repository setup

These extend AGENTS.md, which stays in force (default branch master, versioning, CI runners, the .gitignore and first-commit checks). For .NET, also load zomp-dotnet.

Template files are in templates/ beside this file. Copy them; do not reinvent them.

First commit

1. .gitattributes and .editorconfig from templates/. Two-space indents everywhere unless a stack's formatter decides otherwise (C# 4, Rust's rustfmt). An exception gets its own section with a comment saying why.
2. .gitignore, scoped per the rule in AGENTS.md.
3. A README: what it is, how to build and run it, how to deploy.
4. No license without asking. It is the owner's call.

pnpm and the pre-commit hook

pnpm is the package manager wherever there is a choice, including in repos whose only Node tooling is the hook. Not npm, not yarn.

1. pnpm add -D husky prettier and "prepare": "husky" in package.json (husky 9; husky install is the deprecated v8 form).
2. Copy templates/.husky/pre-commit, templates/scripts/end-of-file.sh and templates/.prettierignore. Add the stack's check at the end of the hook (dotnet format --verify-no-changes ... whitespace, cargo fmt --check).
3. Keep both scripts executable in git: git update-index --chmod=+x .husky/pre-commit scripts/end-of-file.sh (Windows does not record it otherwise).
4. Before the first commit, format what the hook checks, once: pnpm exec prettier --write over the JSON, Markdown and YAML files. Otherwise the first person to touch an untouched file gets a failure they did not cause.
5. Prove it: stage a tab-indented .json and a file without a final newline; the hook must reject both. Then sh .husky/pre-commit all must pass on the whole tree.

No .prettierrc: Prettier's defaults (2 spaces) match .editorconfig.

VS Code

Track these and ignore the rest of .vscode:

/.vscode/*
!/.vscode/tasks.json
!/.vscode/launch.json
!/.vscode/extensions.json

• tasks.json: one task per thing a developer runs (build, preview, dev loop, deploy).
• launch.json: debug configurations for what the tasks run.
• extensions.json: only extensions the repo relies on, each for a reason: the language servers, the debugger a launch.json type needs (CodeLLDB for lldb), esbenp.prettier-vscode, and EditorConfig.EditorConfig (VS Code ignores .editorconfig without it).
• settings.json only for settings every contributor needs; personal ones stay untracked.

No personal hosts, usernames, addresses or absolute paths in any of them. A task that needs a machine or router takes it from the environment ("env": { "ROUTER": "${env:ROUTER}" }), and the script fails clearly when it is unset rather than quietly doing less.

Use ${workspaceFolder} for paths. Background tasks that a launch configuration starts need a problemMatcher with a background section, so VS Code knows when they are ready.

Existing repos

Older repos differ (yarn instead of pnpm, husky install, no newline check). Bring one into line when you are next working in it; do not open a sweep across repos.