skill-loading-patterns

Proactive skill loading uses specific rules based on the operation being performed, such as cloning repositories or starting dev servers, ensuring project-specific skills are loaded first to follow established conventions.

Mapping request keywords to skills involves matching operation terms like git or github to the appropriate skills, preventing incorrect assumptions about repository structure and ensuring proper project setup.

To ensure project conventions are followed, prioritize loading project-specific skills first before general operations, which enforces correct worktree locations, build patterns, and workflow rules automatically.

Avoiding filesystem pattern matching for path discovery prevents agents from incorrectly inferring project conventions and file locations, relying instead on explicit skill rules for accurate path resolution.

Yes, this rule-based skill loading approach defines specific rules for operations like starting dev servers and setting up worktrees, ensuring the correct platform-specific and git skills are loaded first.

The limitation of rule-based skill loading is that it relies on predefined keyword-to-skill mappings and explicit rules, meaning unmapped keywords or novel operations may not trigger the correct proactive skill loading.