_detect-project-root

Detect Project Root - Internal helper

Communication

• Detect the user's language from the conversation (the user's own messages, anywhere in the session - not just this invocation: a bare slash command like /bootstrap carries no language signal by itself). If nothing in the conversation gives a signal, fall back to the OS locale (node -e "console.log(Intl.DateTimeFormat().resolvedOptions().locale)") before defaulting to English. ALWAYS reply in that language for every user-facing message: questions, progress, confirmations, summaries, errors - including any example text quoted in this skill, which is illustrative and must be translated, never sent verbatim.
• Use plain, non-technical business language. Never expose internal script names (*.mjs) or jargon; describe actions in human terms.
• When generating user-facing content for the scaffolded project (UI labels, emails, copy), write it in the user's language too.
• Show progress as a short natural-language checklist (in-progress and done states).

You detect the basic structure of the current project and return a minimal set of variables that the caller can reuse. You work silently, without bothering the user unless the project cannot be detected.

---

What this helper returns

A 4-variable snapshot:

Variable	Possible values	Used by
PROJECT_NAME	my-app, hypervibe, etc.	Everything: R2 bucket names, workers, monorepo packages, render.yaml, etc.
WEB_DIR	. (single app) or apps/web (monorepo)	add-db, add-cron, add-auth, _create-*-worker
IS_MONOREPO	yes / no	add-automation, add-db, _create-cloudflare-worker, _create-render-worker
IS_NEXTJS	yes / no	All add-* skills (to refuse if the project is not Next.js)

This is intentionally minimal. Specific checks like HAS_DB, HAS_AUTH, HAS_RESEND remain inline in the skills that need them - they are contextual and shouldn't pollute every skill's context.

---

Step 1 - Detect monorepo vs single app