skills/llm-integration-policies/SKILL.md
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.
npx skillsauth add mikefullerton/catherding llm-integration-policiesInstall 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.
/claude directory — not scattered across the repo.Every repo should be opted into Graphify (for every LLM that supports it):
pip install graphifyy && graphify installgraphify-out/ added to .gitignore (generated output, not committed).graphifyignore if any directories should be excluded (same syntax as .gitignore)/graphify in a session to generate the initial graphTwo different things. Pick the right one:
/policies/..claude/CLAUDE.md (project scope) or /claude/rules/ (global scope). Written as directives to Claude specifically.Heuristic: If a rule would make sense for a human developer to follow, it's a general policy. If it's "Claude, remember to...", it's a behavioral instruction.
Extensions (skills, rules, agents, MCP integrations, commands, plugins, hooks) are scoped by who they affect:
/claude/<type>/ (e.g. /claude/skills/, /claude/rules/). Must have install/uninstall scripts in /setup/..claude/ (e.g. .claude/skills/, .claude/CLAUDE.md). No install scripts needed — Claude Code picks them up automatically.Full rationale in ~/projects/active/catherding/policies/setup/repo-organization/llm-file-layout.md. See INDEX.md for related policies.
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.
testing
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.