## Problem/Motivation The skills scanner walks the whole project tree, but it only keeps skills from two source types: composer packages (path contains `/vendor/`) and modules (path contains `modules/`). A skills directory inside a theme, such as `web/themes/custom/mytheme/.agents/skills`, is found during the walk but classified as unknown and silently dropped in `SkillsScanner::scanRecursively()`. Themes are a natural place for skills. A theme could ship a skill that describes its component structure, naming conventions, and how design tokens map to components. This would help Figma-to-theme workflows. Profiles have the same gap. ## Proposed resolution - Add a theme path check next to the existing module check. Match `themes/`, `web/themes/`, and `sites/*/themes/`. Use the theme name as the source name. - Add a `discover_themes` config flag, default true, next to `discover_modules`. - Add tests that mirror the module discovery coverage. ## Remaining tasks - Decide whether profiles are in scope for this issue or a follow-up - Implementation and tests