project-detector
Skill0 starsChanged 8 months agoMITView on GitHub
Auto-detects project type from manifest files and folder structure. Use when opening a new project, running /user:init-project, or when Claude needs to understand what stack a project uses.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Data-Wise/crafttheir own version, first seen Oct 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Data-Wise/craft★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commitSkill
- consolidate-learningsSkill
- dailySkill
- debugSkill
- handoffSkill
- init-projectSkill
- learnings-loopSkill
- optimizeSkill
- planSkill
- quick-researchSkill
- reflectSkill
- reviewSkill
- scaffoldSkill
- session-memorySkill
- strategic-compactSkill
- teachSkill
- testSkill
- wrapSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Check these files in order to identify the project:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Stack Detector
Detection Logic
Check these files in order to identify the project:
JavaScript/TypeScript
package.json→ Read "dependencies" and "devDependencies" to identify frameworkreact+vite→ React + Vite projectnext→ Next.js project@angular/core→ Angular projectvue→ Vue.js projectsvelte→ SvelteKit projectexpressorfastifyor@nestjs/core→ Node.js APIreact-nativeorexpo→ React Native mobile
tsconfig.json→ TypeScript enabledtailwind.config.*→ Tailwind CSSvite.config.*→ Vite bundlernext.config.*→ Next.js
Python
pyproject.tomlorsetup.py→ Python projectdjango→ Djangofastapi→ FastAPIflask→ Flasktorchortensorflow→ ML project
requirements.txt→ pip dependenciesPipfile→ pipenv
Rust
Cargo.toml→ Rust projectactix-web→ Actix web frameworktokio→ Async Rust
Go
go.mod→ Go project
Other
Gemfile→ Ruby/Railscomposer.json→ PHP/Laravelbuild.gradleorpom.xml→ Java/Kotlinpubspec.yaml→ Flutter/DartDockerfile→ Containerized
Structure Indicators
client/+server/→ Fullstack monorepopackages/orapps/→ Monorepo (Turborepo/Nx)src/components/→ Component-based frontendsrc/routes/orsrc/pages/→ Page-based routing
After Detection
Output a summary:
Detected: [Framework] + [Language] + [Styling] + [Testing] + [Bundler]
Structure: [monolith/monorepo/fullstack]
Key commands: dev, build, test, lint (from scripts)Then generate appropriate CLAUDE.md content for this specific stack.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

