skill-conditions

Automatic skill activation based on file paths uses glob-based path matching and exclusion rules to trigger specialized expertise when relevant project files change. This reduces manual skill selection and context switching during coding workflows.

Yes, you can trigger specific skills when React or Terraform files change by applying path-filtered activation. It matches file globs and exclusions to dynamically surface the correct specialized skill as soon as matching source files or build manifests are touched.

Dynamic skill discovery works by scanning project-local locations and parent directories to find applicable skills. When file context changes, it coordinates safe activation by injecting the relevant context and matching the updated file paths.

The best way to manage context switching in multi-language projects is implementing a path-based activation model. By defining glob patterns and exclusion rules, the correct expertise for Python, JavaScript, or Rust appears automatically when matching files are edited.

Yes, you need exclusion rules for path matching to coordinate dynamic activation safely. Exclusions prevent unwanted skills from triggering when irrelevant files change, ensuring only the correct specialized skill activates for the specific file paths being edited.

A file watcher might not trigger the correct specialized skill if the glob patterns and exclusion rules are misconfigured. Proper path-based activation requires accurately matching file globs to ensure relevant source files and configs initiate the right expertise.