Discover NL Programming Artifacts

Purpose: Discover NL programming artifacts by path pattern.

Input: directory path, category filter (A, B, or both) Output: classified file list with line counts

Category A — Plugin Artifacts

Patterns to search (relative to target directory):

Category B — Project Config

Category F — Memory Files

Skip Directories

Always skip these directories during traversal:

• node_modules/
• .git/
• target/
• dist/
• build/
• vendor/
• __pycache__/
• .next/
• .venv/

Instructions

1. Receive: directory (absolute path), category ("A", "B", "F", or "both")
2. Use Glob to find files matching each pattern within the directory
3. Filter out any results that fall inside skip directories
4. For each found file, use Read to count lines
5. Return a structured list with entries: { path, category, pattern_matched, line_count }
6. For Category B settings files (.claude/settings.json, .claude/settings.local.json): after discovering the file, flag whether it contains a top-level hooks key — if so, note inline_hooks: true on the entry so the scanner knows to treat it as a hook source as well

Notes

• For commands/**/*.md results, exclude any file whose path contains /commands/shared/ (those match the shared partials pattern instead)
• .gitkeep files are not artifacts — ignore them
• If a file matches multiple patterns, use the first matching pattern in the order listed above (Category A first, then B, then F)
• **/CLAUDE.md in Category B will also match the root CLAUDE.md — deduplicate: if a file was already matched by the root CLAUDE.md pattern, do not add it again
• Category F patterns expand ~ to the user's home directory before globbing