Our review
Bidirectionally syncs configurations between the local project (.claude/) and the global template (~/.claude/template/).
Strengths
- Ensures complete synchronization without accidental overwrites by enforcing a defined order (template first, then project).
- Allows pushing local improvements to the template and pulling template updates into the project.
- Leverages dedicated scripts (template-updater and project-updater) for reliable execution.
Limitations
- Requires manual invocation of external scripts (template-updater and project-updater).
- Does not automatically handle file conflicts; manual copies may be needed.
- Scripts must be accessible via the skill's defined path, which can be fragile.
At the start of a Claude Code session, after improving shared rules or skills, or periodically to keep project and template aligned.
When there are no changes to synchronize, or when working on a solo project without a template.
Security analysis
SafeThe skill only orchestrates usage of other skills and suggests standard version control commands (using 'but' tool) for syncing configuration. No destructive, exfiltrating, or obfuscated actions are present. The allowed tools are appropriate for the task.
No concerns found
Examples
Sync between project .claude/ and ~/.claude/template/.Push my latest .claude/ changes to the template and then pull template updates back.Start of session: sync template into project .claude/.name: sync description: > Synchronize project and template configurations bidirectionally. Runs template-updater then project-updater in correct order. Use when syncing changes between project .claude/ and ~/.claude/template/. allowed-tools: [Bash, Read, Write, AskUserQuestion]
Sync
Bidirectional sync between project .claude/ and ~/.claude/template/.
Why Order Matters
- template-updater first - Push local improvements to template
- project-updater second - Pull template updates to project
Running in wrong order would overwrite local improvements before they're pushed.
Workflow
- Use the Skill tool to invoke
/template-updater- this loads the skill with the correct script path - Handle any file copies needed
- Use the Skill tool to invoke
/project-updater- this loads the skill with the correct script path - Handle any file copies needed
- Summarize what changed
Do NOT guess script paths. Each skill's SKILL.md documents its own script.
After Sync
If any files were copied, commit the changes:
Project changes:
but status
but commit <branch> --only -m "chore: sync claude config from template"
Template changes:
cd ~/.claude && but status
but commit <branch> --only -m "chore: update template from project"
When to Use
- At session start (get latest template updates)
- After improving shared skills/rules (push to template)
- Periodically to keep project and template aligned
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.