Package Sync FAQs

Question 1

How does it handle naming conflicts between different packages?

Accepted Answer

The skill uses a priority-based linking system. If a component exists in both sax-meta and sax-core, it prioritizes sax-meta to resolve the conflict and ensure the correct version is linked to your workspace.

Question 2

When should I use this skill?

Accepted Answer

You should trigger this skill after making changes to an Agent or Skill, after updating git submodules, or when preparing for deployment after versioning to ensure all directory links are correctly mapped.

Question 3

How does this improve my Claude Code developer workflow?

Accepted Answer

It eliminates the manual overhead of managing complex file structures and broken symbolic links. By automating the 'plumbing' of your dev environment, it allows you to focus on building features rather than fixing environment issues.

Question 4

What does the Package Sync skill do?

Accepted Answer

Package Sync automates the synchronization between SAX package sources and your .claude directory. It manages symbolic links for Agents, Skills, and Commands, ensuring your local environment remains consistent with the source repositories.

Question 5

Can I verify my environment without actually changing files?

Accepted Answer

Yes, the skill includes a --check-only integrity verification mode. This reports on broken links, missing components, or synchronization gaps without applying any actual changes to your file system.

Package Sync

Package Sync

Key Features

Use Cases

Key Features

Use Cases