internal/skills/content/sync-claude-md/SKILL.md
Sync per-folder CLAUDE.md and AGENTS.md files with context-aware content. Use after structural changes, adding new directories, refactoring, or periodic maintenance to keep folder-level AI instructions current.
npx skillsauth add ar4mirez/samuel sync-claude-mdInstall 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.
Recursively scan project directories and create or update per-folder CLAUDE.md and AGENTS.md files with auto-detected content including languages, purpose, key files, and test indicators.
# Sync all directories (recursive, unlimited depth)
samuel sync
# Preview changes first
samuel sync --dry-run
# Only top-level directories
samuel sync --depth 1
# Overwrite user-customized files
samuel sync --force
The command reports what happened for each directory:
After syncing, review generated files and add folder-specific instructions:
samuel sync won't overwrite your changes next time — remove it to protect the file from future updates| Detection | Examples |
|-----------|----------|
| Languages | Go, Python, TypeScript, Rust, Java, etc. (by file extension) |
| Purpose | cmd/ → entry points, internal/ → private packages, tests/ → test files |
| Key files | main.go, package.json, Dockerfile, Makefile |
| Tests | *_test.go, test_*.py, *.spec.ts, *.test.js |
| Condition | Action |
|-----------|--------|
| File doesn't exist | Create new file |
| File has <!-- Auto-generated by Samuel marker | Update (overwrite) |
| File exists without marker | Skip (user-customized) |
| --force flag | Always overwrite |
If the CLI is not available, create per-folder CLAUDE.md files manually:
# folder-name
<!-- Auto-generated by Samuel. Customize with folder-specific instructions. -->
<!-- AI agents load this file when working in this directory. -->
## Purpose
Description of what this folder contains.
## Languages
- Go (10 files)
## Key Files
- `main.go` — Entry point
After running sync, verify the results:
development
Zig language guardrails, patterns, and best practices for AI-assisted development. Use when working with Zig files (.zig), build.zig, or when the user mentions Zig. Provides comptime patterns, allocator conventions, C interop guidelines, and testing standards specific to this project's coding standards.
tools
WordPress framework guardrails, patterns, and best practices for AI-assisted development. Use when working with WordPress projects, or when the user mentions WordPress. Provides theme development, plugin architecture, REST API, blocks, and security guidelines.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs. Use when testing web apps, automating browser interactions, or debugging frontend issues.
tools
Suite of tools for creating elaborate, multi-component web applications using modern frontend technologies (React, Tailwind CSS, shadcn/ui). Use for complex projects requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX pages.