Automated summary
Synchronizes shared rules from a central directory into agent context files.
Strengths
- Centralized rule management preventing duplication
- Automated and ordered propagation of updates
- Built-in timestamp for traceability
- Clear and extensible file structure
Limitations
- Requires a working Python environment
- Limited to files under shared-rules/ directory
- Does not handle conflicts if files are manually altered
When you need to maintain consistent rules across multiple agents or contexts.
For one-off changes that don't require centralized governance.
Security analysis
SafeThe skill instructs running a local Python script to synchronize rule files. It does not contain destructive commands, exfiltration attempts, or obfuscated payloads. The script itself is not provided, but the skill description does not introduce direct risks.
No concerns found
How this analysis is madeExamples
/sync-rulesI've updated the shared rules. Please run /sync-rules to propagate changes to all agent context files.name: sync-rules description: Synchronize shared rules into agent context files and headers. version: 1.1.0 tags: [rules, governance, sync] owner: orchestration status: active
Sync Rules Skill
Synchronize shared rules from shared-rules/ to all agent context files.
Overview
This skill propagates rules from the central shared-rules/ directory to:
CLAUDE.md(this file)- Project-level context files
- Agent-specific overrides
Usage
/sync-rules
Prerequisites
- Python environment available to run
scripts/sync-rules.py.
How It Works
-
Read shared rules:
shared-rules/ ├── core-rules.md ├── coding-standards.md ├── guardrails.md ├── cli-reference.md ├── lessons-learned.md └── agent-overrides/ └── claude.md -
Assemble CLAUDE.md:
- Start with claude-specific header
- Append shared rules in order
- Add lessons learned at end
-
Update timestamp:
<!-- AUTO-GENERATED from shared-rules/ --> <!-- Last synced: 2026-01-22 12:00:00 -->
Execution
python scripts/sync-rules.py
Or manually:
- Read all files from
shared-rules/ - Concatenate in order
- Write to
CLAUDE.md
File Order
agent-overrides/claude.md- Claude-specific rules (header)core-rules.md- Core workflow rulescoding-standards.md- Coding guidelinesguardrails.md- Safety guardrailscli-reference.md- CLI tool referencelessons-learned.md- Lessons from past issues
Validation
After sync, verify:
- [ ] CLAUDE.md updated
- [ ] Timestamp current
- [ ] No merge conflicts
- [ ] Rules are complete
Outputs
- Updated
CLAUDE.mdand any derived context files.
Error Handling
- If sync fails, stop and fix the script or inputs before continuing.
- If timestamps are stale, rerun the sync to avoid mismatched rules.
Examples
/sync-rules
Related Skills
/add-lesson- Add a lesson before syncing rules
When to Sync
Run sync after:
- Adding a new lesson learned
- Updating shared rules
- Before starting a new workflow
- After pulling changes from git
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/sync-shared-rules-mm5t89zw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/sync-shared-rules-mm5t89zw/download' --output '.skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md.part' && mv '.skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md.part' '.skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Prerequisites
- Python environment available to run
scripts/sync-rules.py.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md' && test -s '.skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/sync-rules' && cp -R '.skill-downloads/sync-shared-rules-mm5t89zw' '.claude/skills/sync-rules'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/sync-shared-rules-mm5t89zw'openskills read 'sync-shared-rules-mm5t89zw'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/sync-shared-rules-mm5t89zw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.