From not-my-reforge
Automatically detect and understand project structure, tech stack, conventions, and key files. Provides project context as background knowledge.
How this skill is triggered — by the user, by Claude, or both
Slash command
/not-my-reforge:project-awarenessThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You have the project-awareness skill. When starting work on a project, automatically gather the following context before proceeding with any task.
You have the project-awareness skill. When starting work on a project, automatically gather the following context before proceeding with any task.
Check for these files to determine the tech stack:
package.json → Node.js (check for framework: next, remix, vite, etc.)tsconfig.json → TypeScriptCargo.toml → Rustgo.mod → Gopyproject.toml / setup.py / requirements.txt → PythonGemfile → Rubypubspec.yaml → Flutter/Dartpom.xml / build.gradle → Java/KotlinExtract from package.json scripts, Makefile, or similar:
npm run dev, cargo run, go run .npm run build, cargo build, go buildnpm test, cargo test, go test ./...npm run lint, cargo clippyMap the source code layout:
src/ vs app/ vs lib/ — where does code live?components/ — UI componentsapi/ or routes/ — API endpointsutils/ or helpers/ — shared utilitiestypes/ or interfaces/ — type definitions__tests__/ or tests/ — test filesDetect from existing code:
This skill is automatically invoked as background knowledge. You don't need to run all checks every time — use judgment about which context is relevant to the current task. Prioritize reading:
npx claudepluginhub speson/not-my-reforge --plugin not-my-reforgeExplores project structure, configurations, code patterns, conventions, tests, and dependencies before modifying existing code to understand context and avoid bugs.
Extracts tech stack, project structure, key patterns, and conventions from codebases via package.json scans, find, grep for JS/TS, Python, Go, Rust projects. Use before PRDs or planning.
Analyzes codebase structure, tech stack, patterns, and conventions for project onboarding and exploration.