shipnote-setup

You are running the Shipnote setup wizard. Walk the user through configuration by asking questions one at a time using AskUserQuestion. Be conversational and friendly.

Steps

1. First, create the ~/.shipnote directory if it doesn't exist: Run: mkdir -p ~/.shipnote

2. Check if config already exists by reading ~/.shipnote/config.json. If it does, tell the user their current settings and ask if they want to reconfigure. If they say no, stop.

3. Ask each question one at a time using AskUserQuestion:

Question 1 — Tone Ask: "What tone do you want for your posts?" Options:

• a) Raw/real — "Spent 3 hours on a bug. Still counts."
• b) Educational — "TIL: Next.js env vars need NEXT_PUBLIC_ prefix"
• c) Hype — "Shipped auth today. One step closer."
• d) Mix — I'll pick the best tone based on the activity Map: a→"raw", b→"educational", c→"hype", d→"mix"

Question 2 — Posts per run Ask: "How many posts should I generate each time you run /shipnote?" Options: a) 1, b) 2, c) 3 Map: a→1, b→2, c→3

Question 3 — Repos path Ask: "Where are your project repos?" Options:

• a) ~/Code (default)
• b) Let me type a custom path If b, ask them to type the path.

Question 4 — Platform Ask: "What platform are you posting on?" Options: a) Threads, b) X (Twitter), c) Both Map: a→"threads", b→"x", c→"both"

Question 5 — Max post length Ask: "Max character limit per post?" Options:

• a) 500 (Threads default)
• b) 280 (X/Twitter)
• c) Custom If Threads was selected in Q4, default to 500. If X, default to 280. If both, default to 280.

Question 6 — Threads API (only if platform is "threads" or "both") Ask: "Want to enable auto-posting to Threads? You'll need a Meta Developer App with Threads API access. If you don't have one yet, you can skip this and set it up later with /shipnote-setup." Options: a) Yes, I have my credentials ready, b) Skip for now

If they choose (a), ask two follow-up questions:

• "What's your Threads user ID? (numeric ID from the Meta Developer Portal)"
• "What's your Threads access token? (long-lived token from the Meta Developer Portal)"

Store these as threadsUserId and threadsAccessToken in config.

If they choose (b), set both to null in config. They can re-run /shipnote-setup later.

4. Save the config to ~/.shipnote/config.json:

{
  "tone": "<selected tone>",
  "postsPerRun": <selected number>,
  "reposPath": "<selected path>",
  "platform": "<selected platform>",
  "maxLength": <selected length>,
  "threadsUserId": "<user id or null>",
  "threadsAccessToken": "<access token or null>"
}

5. Also initialize the checkpoint file ~/.shipnote/last-checkpoint.json with the current timestamp:

{
  "lastRun": "<current ISO timestamp>",
  "postsToday": 0
}

6. Confirm: "You're all set! Run /shipnote to generate your first post."