skills

Apply shared engineering principles (YAGNI, deep modules, trusted libraries, separation of concerns, leave it better) when writing or changing code, or when drafting CONTRIBUTING.md. Use whenever the user asks for design guidance, contribution guidelines, how to structure changes, or to follow project engineering principles — even if they do not name this skill.

Initialize or scaffold a repository with standardized project baselines (README, license, tests, lint/types, AGENTS.md, pre-commit, CI, skills). Use when the user asks to set up a new repo, bootstrap project tooling, or apply your standard repo setup — not for routine feature work or code review. Prefer this skill whenever they say "set up this repo", "scaffold", "initialize the project", or want release-please / pre-commit / PyPI trusted publishing as part of initial setup.

Maintain an in-repo markdown wiki under wiki/: init a new wiki, surgically update it after code changes, or answer questions from it. Use for /wiki init, /wiki update, /wiki ask, "generate the wiki", "refresh the docs", "how does X work in this repo" when wiki/ exists, deep-wiki style docs, or keep the wiki in sync — never wipe an existing wiki; prefer small incremental edits. Also use when installing CI that runs wiki update on push.