framework-detectorlisted

# Framework Detector Skill ## Quick Reference **When to Use**: Automatically detect framework in project before loading framework-specific skills **Supported Frameworks**: NestJS, React, Phoenix, Rails, .NET/ASP.NET Core, Blazor **Detection Method**: Multi-signal analysis with weighted confidence scoring ## Usage ### Basic Detection ```javascript const FrameworkDetector = require('./detect-framework'); const detector = new FrameworkDetector('/path/to/project'); const result = await detector.detect(); console.log(result.primary); // "nestjs" console.log(result.confidence); // 0.92 console.log(result.alternates); // [{ framework: "dotnet", confidence: 0.45 }] ``` ### CLI Usage ```bash # Detect framework in current directory ./detect-framework.js # Detect framework in specific project ./detect-framework.js /path/to/project # Output format (JSON) { "primary": "react", "confidence": 0.89, "alternates": [], "details": { ... } } ``` ## Detection Signals ### 1. Package Manager (Weight: 10) - **Node.js**: `package.json` dependencies - **Ruby**: `Gemfile` gems - **Elixir**: `mix.exs` dependencies - **.NET**: `*.csproj` PackageReferences ### 2. Files (Weight: 8-9) - Required: Framework-specific config files - Optional: Common project structure files - Wildcards: Pattern matching (e.g., `*.csproj`) ### 3. Imports (Weight: 7-8) - Code pattern analysis in source files - Regex-based matching - File sampling for performance (max 20 files) ### 4. Boost Factors (Mu