mikefullerton/file-organization-policies
skills/file-organization-policies/SKILL.md
Use when creating a new file or directory in an unfamiliar location, or when reviewing whether a file is in the right place. Enforces directory/file naming and encapsulation rules.
testing
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add mikefullerton/catherding file-organization-policiesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 2:47 AM84.9s1 file scanned
SKILL.md
- name:
- file-organization-policies
- description:
- Use when creating a new file or directory in an unfamiliar location, or when reviewing whether a file is in the right place. Enforces directory/file naming and encapsulation rules.
File Organization — MANDATORY
Directories
- Encapsulate coupled files together in directories named for their purpose.
- Avoid loose files in the repo root, or in directories that already contain encapsulated subdirectories.
- Lowercase directory names only.
- No hyphens in directory names.
Files
- Kebab-case for file names that contain a delimiter:
my-file.md, notmy_file.mdormyFile.md. - Language conventions win where they conflict with kebab-case:
- Swift:
PascalCase.swift - Python modules:
snake_case.py
- Swift:
- When in doubt, kebab-case.
Allowed loose files in the repo root
Only these belong at the top level:
- Any dot-prefixed file or directory (
.gitignore,.gitattributes,.claude/,.vscode/, etc.) *.code-workspace(VS Code workspace files)README.md
Anything else goes in a subdirectory.
Reference
Full rationale in ~/projects/active/catherding/policies/setup/repo-organization/file-organization.md. See INDEX.md for related policies.
Related Skills
mikefullerton/general-principles
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 22, 2026
mikefullerton/yolo
tools
VerifiedTrustedCommunity
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
SKILL.mdUpdated Apr 21, 2026
mikefullerton/setup-and-install-scripts
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 21, 2026
mikefullerton/new-repo-scaffold
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 21, 2026