config-sync-overview
Provide structured config-sync system and directory overview. Use when config-sync architecture guidance is required.
When & Why to Use This Skill
This Claude skill serves as a centralized architectural guide for the config-sync system, providing a structured overview of its eight-phase pipeline, backup strategies, and tool mappings. It ensures high-fidelity reasoning by extracting and normalizing system knowledge from core documentation, specifically focusing on .claude directory semantics and configuration precedence.
Use Cases
- System Architecture Guidance: Providing developers and agents with a stable, eight-phase sequence (collect, analyze, plan, etc.) for planning complex configuration synchronization tasks.
- Directory Structure Mapping: Identifying specific configuration directories, key files, and formats for target tools to ensure accurate file operations and tool selection.
- Configuration Governance: Explaining the semantics and priority of core .claude directories like rules/, commands/, and backup/ to maintain system integrity during migrations or updates.
- Documentation-Grounded Troubleshooting: Resolving questions about configuration precedence and backup layouts by referencing verified documentation instead of making heuristic guesses.
| name | config-sync-overview |
|---|---|
| description | Provide structured config-sync system and directory overview. Use when config-sync architecture guidance is required. |
Purpose
Provide a single, governed entry point for config-sync system knowledge, including phase pipeline, backup strategy, target tool mapping, and .claude directory semantics derived from documentation.
IO Semantics
Input: Questions or tasks that require understanding of config-sync phases, backup layout, target tool directories, or .claude directory structure. Output: Normalized descriptions of phases, directories, and configuration precedence with pointers to relevant documentation sections. Side Effects: None. Read-only access to documentation files.
Deterministic Steps
Documentation Loading
- Load docs/config-sync-guide.md for config-sync architecture, phases, and target tool mapping.
- Load docs/directory-structure.md for .claude directory semantics and configuration priority.
Phase Pipeline Extraction
- Confirm the eight config-sync phases: collect, analyze, plan, prepare, adapt, execute, verify, report.
- Record which phases handle backups, verification, and reporting.
- Expose this pipeline to agents as a stable sequence for planning and reasoning.
Target Tool Mapping
- Extract target tools and their configuration directories from the guide.
- For each tool, record config directory, key files, and configuration format.
- Provide this mapping to agents when selecting targets or resolving directory questions.
Directory Semantics Extraction
- Extract meanings of core .claude directories relevant to config-sync: rules/, commands/, docs/, backup/, projects/.
- Record configuration priority and migration guidance where applicable.
- Provide concise explanations instead of full documentation dumps.
Answer Generation
- When invoked by agent:config-sync or related agents, answer using extracted pipeline, mappings, and directory semantics.
- Avoid inventing new paths or phases; answer strictly within the documented model.
- When information is missing, instruct agents to consult the underlying documentation rather than guessing.
Validation Criteria
- Phase pipeline in this skill matches docs/config-sync-guide.md.
- Target tool directory mapping matches docs/config-sync-guide.md.
- .claude directory semantics match docs/directory-structure.md.
- Responses remain consistent with documentation and do not introduce undocumented behaviors.