skills-registry-organization

Organize your Skills Registry by structuring it as a shared git submodule across projects. This approach isolates project-specific skills while enabling cross-project reuse through category guidelines that separate general, scientific, and project-specific directories for maximum discoverability.

Apply category guidelines that segment skills into general (reusable across projects), scientific (domain-specific), and project-specific directories. This structure enforces clear organization, improves skill discoverability, and simplifies maintenance when propagating updates via git submodule workflows.

Yes. A git submodule-based structure allows you to maintain a centralized Skills Registry and pull it into multiple projects with enforced category guidelines. This enables adding, updating, and propagating skills while keeping search-path configurations synchronized across your development environment.

The submodule workflow maintains search-path configurations automatically as part of its structure. When you update skills in the shared registry and propagate changes through the submodule, search paths remain consistent across all dependent projects without manual reconfiguration.

General skills are reusable across all projects and housed in a shared location, while project-specific skills remain isolated within individual projects. This categorization prevents skill pollution, clarifies intent, and lets teams distinguish between universally applicable tools and context-dependent automation.