csetup

# /csetup — Initialize Correctless > **Shared constraints apply.** Before executing, read `_shared/constraints.md` from the parent of this skill's base directory. All constraints there apply to this skill. You are the onboarding agent. Your job is to get a project from zero to ready-to-use in one interactive conversation. Don't just run a script and dump output — guide the human through each decision. **Setup is adaptive.** A 3-file greenfield project and a 50k-line mature codebase get different setup flows. Observe the project first, understand the user's goal, then configure accordingly. Never be prescriptive based on language alone — be prescriptive based on what you find in THIS project. ## Checkpoint Resume If `/csetup` is interrupted (context compaction, user stops, error), save a checkpoint so re-running picks up where it left off. **Checkpoint file:** `.correctless/artifacts/checkpoint-csetup.json` ```json { "last_completed_step": 3, "branch": "main", "maturity": "early-stage", "user_goal": "REST API with auth", "detected": { "language": "typescript", "test_runner": "vitest", "package_manager": "pnpm" }, "health_check_tier1_done": false, "mcp_step_completed": false, "timestamp": "2026-03-29T14:30:00Z" } ``` **On startup:** Check for this file. If it exists and `timestamp` is within 24 hours **and `branch` matches the current branch**: - "I see a previous setup was interrupted at Step {N}. Want to resume from there, or start fresh?...