Python backend project incorrectly classified as web frontend

[alambertt]

What happened?

Running npx autoskills from the root of a Python backend project classified the repository as a Web frontend and suggested frontend-only skills.

Observed output:

◆ Web frontend detected (from project files)

◆ Select skills to install (3 found)

Frontend
  ❯ ◼ anthropics › frontend-design
    ◼ addyosmani › accessibility
    ◼ addyosmani › seo

This repository is a Python backend project, not a frontend project. At the root it contains requirements.txt and requirements-prod.txt, plus many Python modules and tests (for example app/main.py, common/aws_secrets.py, tests/test_main.py). There is no package.json or common frontend config at the project root.

I expected autoskills to detect this as a Python project, or at least avoid classifying it as a frontend project when the strongest repo signals are Python files and Python dependency manifests.

Steps to reproduce

1. Clone or open a Python backend repository with files like requirements.txt and multiple .py modules.
2. Ensure there is no package.json or common frontend framework config at the project root.
3. Run npx autoskills from the project root.
4. Confirm the install prompt.
5. Observe that autoskills reports Web frontend detected (from project files) and only suggests frontend skills.

Environment

• OS: macOS
• Shell: zsh 5.9
• autoskills: 0.2.4
• Invocation: npx autoskills
• Example repo signals:
  • Present: requirements.txt, requirements-prod.txt, many .py files
  • Absent at root: package.json, frontend config files