project-setuplisted

# Project setup Writes `.claude/project-profile.md`: one file describing this codebase, read by every other engineering skill in this collection. Without it those skills stop and point here, rather than guessing your stack and generating code that does not match your conventions. Run it once per repository. Re-run it when the stack changes. ## Why a shared profile The alternative is each skill hardcoding a stack, paths and deploy commands. That works for exactly one project and silently misfires on every other. One profile means the skills stay generic and your project details live in your repo, where they belong and where you can edit them without touching a skill. ## How to run it **Detect first, then confirm. Never invent.** Read what the repo already tells you before asking anything: | Source | Tells you | |--------|-----------| | `package.json` | Scripts, framework, test runner, package manager | | lockfile name | npm, pnpm, yarn or bun | | `tsconfig.json` paths | Import aliases | | top-level directories | Where source, tests and migrations live | | `.github/workflows/` | The CI pipeline, which is the real build and test contract | | config files (`vercel.json`, `supabase/`, `Dockerfile`, `fly.toml`) | Where it deploys | | `README.md` | Everything the author thought worth saying | Then present what you found and ask the user to confirm or correct it. A wrong detected value that the user silently accepts is worse than a question, so show your evidence: "found `np