library-detectionlisted

# Library Detection Skill Automatically detect the technology stack of a project by analyzing package manifests and configuration files. Returns structured data for use in onboarding, documentation discovery, and tool configuration. ## Variables | Variable | Default | Description | |----------|---------|-------------| | SCAN_DEPTH | 3 | Max directory depth to search for manifests | | INCLUDE_DEV_DEPS | true | Include development dependencies in analysis | | DETECT_FRAMEWORKS | true | Identify frameworks from dependencies | | DETECT_TEST_TOOLS | true | Identify test frameworks and runners | | OUTPUT_FORMAT | json | Output format: json, markdown, or toon | ## Instructions **MANDATORY** - Follow the Workflow steps below in order. Do not skip steps. 1. Scan for package manifests in the project 2. Parse each manifest to extract dependencies 3. Classify dependencies into categories 4. Detect frameworks and test tools from dependency patterns 5. Output structured stack summary ## Red Flags - STOP and Reconsider If you're about to: - Assume a framework without checking imports or config files - Skip manifest files because "the project is simple" - Hardcode framework versions instead of reading from manifests - Report a library without verifying it's actually used **STOP** -> Read the manifest files -> Verify with imports/configs -> Then report ## Workflow ### 1. Discover Manifests Scan for these files (in order of priority): | File | Language | Parser | |------|---------