菜单
VEDA configuration menu. Discovery hub for setting up workflows, registering Slack channels, configuring style guide, archiving projects, and surfacing what else VEDA can do. Use when the user says /setup, "configure VEDA", "what can VEDA do", "set up X", "show me the menu".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
VEDA archival workflow. Moves finished projects to projects/_archive/ and updates all references. Never deletes — always preserves. Use when the user says /archive, "I'm done with [project]", "archive [project]", "close out [project]", "wrap up [project]".
VEDA gap-finding interview. Guided questions to surface what VEDA could do for the user that it isn't already. Ends with one concrete suggestion, not a feature list. Use when the user says /brainstorm, "what else can you help with", "I feel like I'm missing something", "what should I set up next".
VEDA morning briefing. Pulls calendar, Gmail, and Slack, surfaces overdue and due-today action items, and writes a structured briefing to today's journal. Use when the user says /morning, "good morning", "morning briefing", or "what's my day look like".
VEDA first-time setup. Conversational interview that fills in CLAUDE.md and MEMORY.md placeholders so the user does not have to edit those files manually. Use when the user opens VEDA for the first time, when placeholders like [YOUR NAME] are still present in CLAUDE.md, or when the user says /onboard, "onboard me", "set me up", "first time".
VEDA meeting prep. Pulls person profile, project context, recent meetings, open action items, and live email/Slack data for a specific meeting. Use when the user says /prep [meeting name or person], "prep me for", "what do I need to know for", or "what's the context on [person/meeting]".
VEDA voice and tone setup. Captures the user's writing style so VEDA can draft emails, social posts, replies, and other messages in their voice. Use when the user says /style, "teach you my voice", "match how I write", "draft like me", "set up style guide".
基于 SOC 职业分类
| name | veda-setup |
| model | claude-sonnet-4-6 |
| description | VEDA configuration menu. Discovery hub for setting up workflows, registering Slack channels, configuring style guide, archiving projects, and surfacing what else VEDA can do. Use when the user says /setup, "configure VEDA", "what can VEDA do", "set up X", "show me the menu". |
Show the user a numbered menu of configurable VEDA workflows. Route to whichever they pick. Repeatable — run anytime.
Read CLAUDE.md, MEMORY.md, and focus/CURRENT.md. Check whether the following are configured:
test -f style/style-guide.md && echo "style:configured" || echo "style:missing"
test -f rhythms/RECURRING.md && echo "rhythms:configured" || echo "rhythms:missing"
grep -c "^| " slack/channel-summaries/_registry.md # tracked channel count
ls projects/*.md 2>/dev/null | wc -l # active project count
Use this state to mark menu items as (set up) or (not set up yet).
"What would you like to set up? Pick a number, name, or just describe what you need.
- Re-run onboarding — re-do the first-time interview (use if your situation has changed)
- Teach me your voice (set up | not set up yet) — so I sound like you when drafting on your behalf —
/style- Register Slack channels — channels I should watch in morning briefings — (N tracked)
- Set up recurring rhythms (set up | not set up yet) — gym, family calls, recurring obligations —
rhythms/RECURRING.md- Create a project — index card or full hands-on workspace
- Archive a project — move a finished project to
projects/_archive/- Update focus areas — what's primary right now →
focus/CURRENT.md- Brainstorm gaps — guided questions to surface what would help most —
/brainstorm- Configure API integrations — Google Calendar, Gmail, Slack, GitHub
Or tell me what you actually need and I'll figure it out."
Map the user's pick to the matching skill or inline workflow:
| Pick | Action |
|---|---|
| 1 | Re-run .claude/skills/onboard/SKILL.md (skip Step 1 detection — they invoked it) |
| 2 | Run .claude/skills/style/SKILL.md |
| 3 | Open slack/channel-summaries/_registry.md, ask for channel name + reason + priority, append a row, confirm |
| 4 | If rhythms/RECURRING.md does not exist, copy rhythms/_template.md to rhythms/RECURRING.md and interview the user about their weekly/monthly/annual recurring events. If it exists, open it and ask what to add. |
| 5 | Inline: ask if it's a light index-card project (projects/{slug}.md) or hands-on directory project (projects/{slug}/ with local CLAUDE.md and BRIEF.md). Then create from the appropriate template. |
| 6 | Run .claude/skills/archive/SKILL.md |
| 7 | Open focus/CURRENT.md, show current state, ask what changed, rewrite. Archive prior version to focus/archive/YYYY-QN.md first. |
| 8 | Run .claude/skills/brainstorm/SKILL.md |
| 9 | Open CLAUDE.md, walk through the Available API Integrations table, remove rows the user is not using, add any missing ones. Note that connecting the integrations themselves happens in Claude Code settings, not here. |
After completing one item:
"Want to set up anything else, or are you good?"
If done:
"Run /setup anytime."