← ClaudeAtlas

cold-start-interviewlisted

Set up Lode for first use. Use this skill when the user runs "/lode:cold-start-interview", asks to configure Lode, or needs help creating a Lode config for persistent memory across sessions. Triggers on phrases like "configure Lode", "set up Lode", "初始化 Lode", "配置 Lode".
KKenny0/Lode · ★ 1 · AI & Automation · score 62
Install: claude install-skill KKenny0/Lode
# Lode Cold-Start Interview Configure Lode's two-layer config: global user preferences and per-project identity. Lode separates concerns between **what's shared** (knowledge vault path, reporting preferences) and **what's project-specific** (project name, project slug). The global config lives at `~/.lode/config.yaml`; project identity lives at `{project-root}/.lode/config.yaml`. The interview detects context and writes to the appropriate target. ## Goal Create or update valid Lode configuration: **Global config** (`~/.lode/config.yaml`): - `knowledge_vault` - `profile.report_language` - `profile.weekly_mode` - `profile.team_context` - `artifact_index.enabled` - `auto_capture.enabled` **Project config** (`{project-root}/.lode/config.yaml`, when CWD is a project repo): - `project_slug` - `profile.project_name` Then register the project in `{vault}/raw/projects.json`. If an existing config is present, preserve fields that are unrelated to this interview, including `daily_note`, `weekly_outline`, `monthly_review`, and any custom keys. ## Step 0: Scope Detection — MUST Complete Before Step 1 **CRITICAL**: Step 0 is a mandatory gate. You MUST read both config files (if they exist) and check completeness BEFORE asking any questions. Do not skip to Step 1 until Step 0 is done. Check the current working directory: 1. Is there a `.git/` directory or `.lode/` directory in CWD or its parents? - **Yes**: This is a project setup. The interview will write project identity