skills/new-repo-scaffold/SKILL.md
Use when creating a new repo (git init, gh repo create, scaffolding a new project) or when a repo is missing README/LICENSE/.gitignore/.claude/CLAUDE.md. Enforces the "every repo must have" checklist and documentation layout.
npx skillsauth add mikefullerton/catherding new-repo-scaffoldInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Every repo under ~/projects/ must have these files in the root before work proceeds. When creating a new repo or noticing any are missing, create them — but follow the rules below, don't just drop templates.
README.md — describes what the repo is. Keep it current as the repo evolves.LICENSE — ask before choosing. Default is All Rights Reserved:
Copyright (c) <year> <author>. All rights reserved.
Alternative: MIT. Do not add a license without asking the user..gitignore — on macOS, always ignore .DS_Store..claude/CLAUDE.md — project-specific Claude instructions. Never CLAUDE.md in the repo root. At minimum covers: what the repo is, its directory structure, how to build/run it. A placeholder is fine — the goal is Claude is oriented on first session.If the repo has documentation, it goes in /docs:
/docs ← general docs
/docs/planning ← specs, proposals, design decisions
/docs/research ← background reading, spike notes, references
Exceptions: SKILL.md stays inside its skill dir; README.md stays co-located with the code it documents. When in doubt, /docs.
mysetup, not my-setup).Full rationale across these policy files in ~/projects/active/catherding/policies/setup/repo-organization/:
Start at INDEX.md to navigate.
development
Use whenever writing, modifying, refactoring, or reviewing code, or when making any design decision — including small ones. Loads the 21 cookbook principles (simplicity, yagni, fail-fast, explicit-over-implicit, separation-of-concerns, design-for-deletion, etc.) as heuristics for judgment calls about code shape, module boundaries, and what to build. Applies across all languages and project types.
tools
Toggle per-session YOLO mode (auto-approve permissions with configurable deny list). Use when --dangerously-skip-permissions is broken. /yolo on, /yolo off, /yolo install, /yolo uninstall, /yolo configure, /yolo status
development
Use when authoring or modifying install/uninstall scripts, or when creating a /setup directory for a repo that requires developer setup steps. Enforces the /setup layout, install/uninstall naming, and supporting-files location.
development
Use when a file imports an LLM SDK (anthropic, openai, langchain, etc.), when scaffolding LLM features, or when placing Claude-specific files in a repo. Enforces the "do not assume Claude" rule, the /claude directory convention, Graphify opt-in, and the rules-vs-behavioral-instructions split.