Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/foundation:detect project-pathFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
--- 🚨 **EXECUTION NOTICE FOR CLAUDE** When you invoke this command via SlashCommand, the system returns THESE INSTRUCTIONS below. **YOU are the executor. This is NOT an autonomous subprocess.** - ✅ The phases below are YOUR execution checklist - ✅ YOU must run each phase immediately using tools (Bash, Read, Write, Edit, TodoWrite) - ✅ Complete ALL phases before considering this command done - ❌ DON't wait for "the command to complete" - YOU complete it by executing the phases - ❌ DON't treat this as status output - it IS your instruction set **Immediately after SlashCommand returns, st...
🚨 EXECUTION NOTICE FOR CLAUDE
When you invoke this command via SlashCommand, the system returns THESE INSTRUCTIONS below.
YOU are the executor. This is NOT an autonomous subprocess.
Immediately after SlashCommand returns, start executing Phase 0, then Phase 1, etc.
See @CLAUDE.md section "SlashCommand Execution - YOU Are The Executor" for detailed explanation.
CRITICAL: All generated files must follow security rules:
@docs/security/SECURITY-RULES.md
Key requirements:
your_service_key_here.env files with .gitignore.env.example with placeholders onlyArguments: $ARGUMENTS
Goal: Analyze project structure and dependencies to detect the complete tech stack, then populate .claude/project.json with framework, languages, AI SDKs, and architecture information
Core Principles:
This commands has access to the following skills from the foundation plugin:
To use a skill:
!{skill skill-name}
Use skills when you need:
Skills provide pre-built resources to accelerate your work.
Goal: Understand the project structure and locate key files
Actions:
Goal: Load and analyze project files
Actions:
Goal: Prepare detection strategy
Actions:
Goal: Execute detection with agent
Actions:
Launch the stack-detector agent to analyze the project and detect the complete tech stack.
Provide the agent with:
Goal: Verify detection results
Actions:
Goal: Report what was detected
Actions:
npx claudepluginhub vanman2024/dev-lifecycle-marketplace --plugin foundation/cc-bootstrapScans repository to detect full tech stack and generates .claude/ architecture: CLAUDE.md, rules, agents, skills, settings.json, .mcp.json, and docs/context files. Supports --dry-run and --audit.
/initDetects project tech stack from root files (Shopify priority, then Next.js, React, etc.) and creates or updates project.json.
/detectAnalyzes current directory to detect project type, tech stack, structure pattern, and configuration recommendations with evidence in markdown report.
/initAuto-detects project stack (framework, language, DB/ORM, auth, styling) by scanning key files and package.json, then saves as Nemp memories.
/setupDetects project tech stack from manifest files and generates CLAUDE.md, PostToolUse hooks, agent templates, and project-stack.json. Supports --dry-run preview.
/create-tech-stackAnalyzes codebase and configs to generate tech stack documentation covering technologies, architecture, patterns, and deployment details via interactive Q&A. Saves to .claude/skills/2-tech-stack.mdc.