@rayburst/cc 3.0.3 → 3.1.0

package/skills/init/SKILL.md

@@ -8,17 +8,11 @@ user-invocable: true
 
 # rb:init — Project Config Setup
 
-Initialize `.claude/rb-config.md` with API connection details, project URL, board selection, and user credentials. Other `rb:` skills read this file automatically.
-
-## Prerequisites
-
-The `RAYBURST_API_KEY` environment variable must be set before the plugin's MCP server can connect. If not set, guide the user to set it.
+Initialize `.claude/rb-config.md` with API connection details, project URL, board selection, and user credentials. The plugin's MCP server and hooks read this file automatically.
 
 ## MCP Tool Prefix
 
-All MCP tools in this skill use the prefix: `mcp__plugin_rayburst_rayburst__`
-
-Example: `mcp__plugin_rayburst_rayburst__rb_ping`
+All MCP tools use: `mcp__plugin_rayburst_rayburst__`
 
 ---
 
@@ -56,24 +50,44 @@ Ask the user for their Rayburst API key:
 ```
 Rayburst API Key
 Enter your API key (starts with rb_user_...):
-Get one at https://www.rayburst.app/settings/api-keys
+Get one at https://www.rayburst.app/profile?tab=mcp-agents
 ```
 
 Validate: non-empty, starts with `rb_`. Store as `api_key`.
 
-Then verify the connection works:
+---
+
+### Step 3: Write Minimal Config & Verify
+
+**Before continuing with other prompts**, write a minimal config file so the MCP server can connect:
+
+```bash
+mkdir -p .claude
+```
+
+Write `.claude/rb-config.md` with just the API section:
+
+```markdown
+# Rayburst Project Config
+
+## API
+- API Key: <api_key>
+- API URL: https://api.rayburst.app/api/v1/mcp
+```
+
+Now verify the connection works:
 
 ```
 mcp__plugin_rayburst_rayburst__rb_ping()
 ```
 
-**If ping fails**, tell the user the key may be invalid or the API is unreachable. Ask them to double-check and re-enter.
+**If ping fails**, the key may be invalid or the API unreachable. Ask the user to double-check and re-enter. Re-write the config and retry.
 
-> **Note:** The API key is stored in `.claude/rb-config.md`. If the user prefers, they can set `RAYBURST_API_KEY` as an env var instead — the env var takes priority over the config file.
+**If ping succeeds**, continue to Step 4.
 
 ---
 
-### Step 3: Prompt for Project URL
+### Step 4: Prompt for Project URL
 
 Ask the user:
 
@@ -88,7 +102,7 @@ Store as `project_url`.
 
 ---
 
-### Step 4: Select Board
+### Step 5: Select Board
 
 List available boards:
 
@@ -110,44 +124,54 @@ Store the selected `board_id` and `board_slug`.
 
 ---
 
-### Step 5: Identify Projects
+### Step 6: Select Projects
 
-Ask the user which projects this workspace maps to. Show any projects associated with the selected board if available, or ask:
+List available projects in the organization:
 
 ```
-Project IDs
-Enter the frontend project ID (or press Enter to skip):
-Enter the backend project ID (or press Enter to skip):
+mcp__plugin_rayburst_rayburst__rb_list_projects()
+```
+
+Display them numbered and let the user pick one or more:
+
+```
+Available projects:
+  1. Rayburst Frontend (231165df-...) — local
+  2. Rayburst API (7805dae1-...) — github
+  3. Marketing Site (a1b2c3d4-...) — manual
+
+Select project(s) for this workspace (comma-separated numbers, or Enter to skip):
+e.g. 1,2
 ```
 
-Store as `frontend_project_id` and `backend_project_id`.
+Store selected project IDs and names as `projects` list. If only one is selected, store it. If multiple, store all.
 
 ---
 
-### Step 6: Collect Users (loop)
+### Step 7: Collect Users (loop)
 
 Initialize an empty `users` list.
 
 **For each user, ask in sequence:**
 
-**6a. Username / email**
+**7a. Username / email**
 ```
 User <N> — Username or email:
 ```
 
-**6b. Password or env var**
+**7b. Password or env var**
 ```
 User <N> — Password (or $ENV_VAR_NAME to reference an env variable):
 ```
 
 If input starts with `$`, store as-is. Otherwise store literal.
 
-**6c. Description**
+**7c. Description**
 ```
 User <N> — Description (e.g. Admin, Viewer, Editor) [User <N>]:
 ```
 
-**6d. Add another user?**
+**7d. Add another user?**
 ```
 Add another user? (yes / no) [no]:
 ```
@@ -156,9 +180,9 @@ At minimum one user required.
 
 ---
 
-### Step 7: Preview & Write
+### Step 8: Write Full Config
 
-Show formatted preview, then write `.claude/rb-config.md`:
+Write the complete `.claude/rb-config.md` (overwriting the minimal one from Step 3):
 
 ```markdown
 # Rayburst Project Config
@@ -175,8 +199,8 @@ Show formatted preview, then write `.claude/rb-config.md`:
 - Slug: <board_slug>
 
 ## Projects
-- Frontend: <frontend_project_id>
-- Backend: <backend_project_id>
+- <project_name_1>: <project_id_1>
+- <project_name_2>: <project_id_2>
 
 ## Users
 
@@ -190,21 +214,19 @@ Show formatted preview, then write `.claude/rb-config.md`:
 
 ---
 
-### Step 8: Confirmation Summary
+### Step 9: Confirmation Summary
 
 ```
 Config saved to .claude/rb-config.md
 
+  API Key     : <first 12 chars>...
   Project URL : <project_url>
   Board       : <board_slug> (<board_id>)
-  Projects    : Frontend: <id>, Backend: <id>
+  Projects    : <N> project(s) selected
   Users       : <N> user(s) configured
 
-Next steps:
-  /rb:status                    — Show feature atlas and board status
-  /rb:plan <task>               — Plan a feature with board card
-  /rb:sync <task>               — Sync a task to the feature atlas
-  /rb:implement <cardId>        — Implement a board card
+Rayburst is now active. On your next session, Claude will automatically
+have your feature atlas and board context. No commands needed — just code.
 ```
 
 ---
@@ -215,3 +237,4 @@ Next steps:
 - **At least one user required**
 - **URL must start with `http://` or `https://`**
 - **`.claude/` directory must exist** — create with `mkdir -p .claude` before writing
+- **Write minimal config before pinging** — the MCP server reads from rb-config.md, not env vars