beam-ai-team/setup

Setup

Run a compact, Prism-first onboarding flow. Prefer native Prism surfaces over Beam Next filesystem conventions.

Safety Contract

Require explicit user approval before creating goals, projects, source connections, saved summaries, or local files. Explaining setup options and drafting a setup summary do not require approval.

Mode Selection

• quick-start: user is new or asks to set up everything.
• personalize: user wants Prism to understand their role, goals, preferences, or work context.
• workspace: user wants to organize sources, files, projects, or Knowledge Base material.

If the user does not choose a mode, start with quick-start and keep the flow short.

Prism Setup Principles

1. Use Prism-native concepts: Goals, Projects, Tasks, Knowledge Base / Sources, Agents, Skills, and Integrations.
2. Do not instruct users to edit .claude/settings.local.json, .vscode/settings.json, user-config.yaml, or old Beam Next folders as part of Prism onboarding.
3. Do not assume 02-memory/, 03-projects/, or 04-workspace/ exist unless the user explicitly says they are using a Beam Next workspace.
4. Deliver value before teaching architecture: capture a goal, connect a source, or plan a first project.
5. When Prism APIs/UI are available, use them. When only chat is available, produce a clear setup summary the user can apply in Prism.

Quick-Start Flow

1. Ask what the user is trying to accomplish with Prism in one practical sentence.
2. Capture or refine one concrete goal with success criteria.
3. Identify relevant work context:
   • role or team
   • tools/integrations they use
   • files or sources they want Prism to know
4. Recommend one first project or agent workflow that creates value quickly.
5. Suggest source ingestion through Prism Knowledge Base / Sources if files, repos, transcripts, or docs are mentioned.
6. End with a concise setup summary and one next action.

Personalize Mode

Use when the user asks to personalize Prism, define goals, or teach Prism about their work.

Ask only for information that changes assistant behavior:

• role or operating context
• current priority
• success metric
• communication preference
• important tools, sources, or constraints

Output:

## Prism Personalization Summary

Role/context: ...
Current goal: ...
Success metric: ...
Preferences: ...
Useful sources/tools: ...
Recommended next action: ...

If a Prism goal-creation tool is available, create or update the goal. Otherwise, ask for confirmation before turning the summary into a project plan or saved artifact.

Workspace Mode

Use when the user asks about files, folders, source organization, or Knowledge Base setup.

1. Ask what sources matter: local folders, documents, repos, transcripts, Slack, email, CRM, or project docs.
2. Prefer Prism Knowledge Base / Sources for durable indexed context.
3. Recommend 2-4 source groups with plain labels, not filesystem-heavy structure.
4. Identify any integration setup required through Prism Settings / Integrations.
5. If the user is explicitly using a Beam Next folder workspace, you may map Prism concepts to its folders, but keep the Prism labels primary.

Completion

Finish with:

• what was captured
• what should be added to Prism
• the first concrete action to take next

Do not mark completion by editing YAML. Prism should track onboarding/skill usage through its native telemetry and product state.