[FEATURE] Project Knowledge Base — auto-detect frameworks and generate skill configs

[yusufkaraaslan]

🚀 Feature Description

Add a two-step workflow for automatically detecting a project's tech stack and generating skills for each framework/tool.

Step 1: skill-seekers scan <path>

• Scan project directory for dependency files (package.json, pyproject.toml, build.gradle.kts, Cargo.toml, go.mod, Gemfile, composer.json, etc.)
• Detect frameworks, tools, and libraries in use
• Generate individual config files (one per detected framework) in a user-chosen output directory
• User can review, edit, or remove configs before generation

Step 2: skill-seekers generate <config>

• Takes a single config file and generates the skill
• User runs this for each config they want to generate
• Uses the config as a template and scrapes the latest docs for that framework version

Config vs Scrape

• Use existing presets (24+) as templates when available
• Update from the latest documentation source for the detected version
• Fall back to fresh scrape when no preset exists

Storage/State

• Let the user choose where configs and generated skills are stored (CLI flag or config option)
• On re-run of scan, detect what changed (new deps, version bumps, removed deps) and update configs accordingly

Output Structure

• Individual config per framework (e.g., react.json, django.json, playwright.json)
• Plus a project codebase skill (separate from framework skills)
• All configs are independent — user generates each one separately

Implementation Notes

• Reuse existing source_detector.py patterns for framework detection
• Leverage existing preset configs as starting points
• The scan command produces configs; generate command consumes them
• Should detect: languages, frameworks, build tools, test frameworks, CI/CD, linting, etc.

Example Workflow

# Step 1: Scan and generate configs
skill-seekers scan ./my-react-app --output ./skill-configs/
# → Created: react-18.json, typescript.json, jest.json, tailwind.json, vite.json

# Step 2: User reviews configs, then generates each
skill-seekers generate ./skill-configs/react-18.json --output ./skills/
skill-seekers generate ./skill-configs/typescript.json --output ./skills/

# Later: re-scan after adding a new dependency
skill-seekers scan ./my-react-app --output ./skill-configs/
# → Updated: react-18.json (version bump detected)
# → Created: prisma.json (new dependency)