Getting started with CodeSpring

Connect, say where the project is, name one next step. Keep it short — then hand off.

Uses the codespring skill's references/project-state.md (state detection, the five questions, the three stages), references/pitfalls.md, and its scripts/ (deterministic state detection).

Step 1 — Connect

1. CLI installed? If codespring is missing: npm i -g @codespring-app/cli.
2. Authenticated? codespring auth status. If not, ask them to run codespring auth login and wait. (Running it also refreshes an expired token.)
3. Project linked? codespring status.
   • Linked → note the name and continue.
   • Not linked → link an existing project (codespring projects → codespring init --project <id> --force), or create one. If it must live in a team workspace, they create it in the web app first — project create ignores --org and there is no way to move or delete a project from the CLI (pitfalls.md).
   • Always trust the local .codespring/config.json for which project is active, and print the projectId.

Step 2 — Say where the project is

Run the state-detection scripts rather than eyeballing the CLI output — the summary must be identical every run. They live in the codespring skill, which installs alongside this one, so the path is relative to this skill's folder; resolve it to an absolute path first, because your working directory will be the user's repo.